[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f1b300lqgtfmoj":3,"$f250wz8h39yydc":8,"$f110bpiyv6m3cg":29,"$f2ht2cy1abfnnk":33,"$fu4akmdn3ywp":37,"toc--1864410704-5-5":41},{"description":4,"domain":5,"id":6,"keywords":4,"title":7},"","api.kongjs.com",1,"默认",[9,20,24],{"children":10,"icon":4,"id":11,"linkType":12,"linkUrl":13,"parentId":14,"sort":15,"status":16,"target":17,"title":18,"visible":19},null,"447369447469600768","URL","\u002F","0",0,"1","_self","首页",true,{"children":10,"icon":4,"id":21,"linkType":12,"linkUrl":22,"parentId":14,"sort":15,"status":16,"target":17,"title":23,"visible":19},"447369693859794944","\u002Fnotes","笔记",{"children":10,"icon":4,"id":25,"linkType":26,"linkUrl":27,"parentId":14,"sort":15,"status":16,"target":17,"title":28,"visible":19},"447369977960976384","PAGE","\u002Fabout","关于我",{"category":10,"categoryId":10,"cover":10,"description":4,"fileId":10,"id":30,"publishAt":10,"tags":31,"title":32},"453170673926283264",[],"云原生微服务",[34],{"children":10,"description":4,"id":35,"noteId":30,"parentId":14,"sort":15,"status":16,"title":36},"453170748048023552","IaaS、PaaS、SaaS + 云原生 + 服务网格 全套通俗详解",{"content":38,"contentType":39,"description":4,"title":36,"wordCount":40},"# IaaS \u002F PaaS \u002F SaaS \\+ 云原生 \\+ 服务网格 全套通俗详解\n\n这五个概念是**云计算 \\& 云原生体系的地基**：IaaS、PaaS、SaaS 是云计算三层交付模型（管「谁负责运维什么」）；云原生是**上云的开发架构理念**；服务网格是**云原生微服务的专属治理架构**。本文全程通俗、无废话、面试商用全覆盖。\n\n## 一、云计算三层模型：IaaS、PaaS、SaaS（核心分层）\n\n核心判断口诀：**从上到下，厂商管得越来越多，开发者管得越来越少**。\n\n### 1\\. IaaS 基础设施即服务（Infrastructure）\n\n**定义**：云厂商帮你搞定**底层硬件基础设施**，你自己管系统、软件、代码。\n\n**交付内容**：虚拟机、服务器、磁盘、网络、负载均衡、带宽、IP。\n\n**谁运维什么**：\n\n- 厂商：硬件、机房、电力、物理网络\n\n- 用户：操作系统、中间件、数据库、代码、部署运维\n\n**通俗比喻**：租毛坯房。房子水电物业房东搞定，装修、家具、布置全部自己来。\n\n**常见产品**：阿里云ECS、腾讯云CVM、AWS EC2、虚拟机、私有服务器\n\n**特点**：最灵活、自由度最高、运维成本最大。\n\n### 2\\. PaaS 平台即服务（Platform）\n\n**定义**：云厂商帮你搞定**基础设施 \\+ 运行平台**，开发者只需要写代码、部署代码。\n\n**交付内容**：容器环境、JDK、Tomcat、数据库、缓存、消息队列、开发运行平台。\n\n**谁运维什么**：\n\n- 厂商：硬件、系统、中间件、数据库、运行环境、扩容基础能力\n\n- 用户：仅负责业务代码开发、业务配置\n\n**通俗比喻**：租精装公寓。房子装修家电齐全，你只需要拎包入住、布置自己的物品（写业务）。\n\n**常见产品**：K8s平台、阿里云SAE、腾讯云TCB、Redis云服务、MySQL云数据库\n\n**特点**：解放运维，专注业务，是**云原生核心依赖层**。\n\n### 3\\. SaaS 软件即服务（Software）\n\n**定义**：云厂商直接交付**成品软件**，用户无需开发、无需部署、无需运维，直接开箱即用。\n\n**交付内容**：完整的在线软件、业务系统。\n\n**谁运维什么**：\n\n- 厂商：底层全部运维、更新、扩容、故障修复\n\n- 用户：仅使用软件功能、配置业务参数\n\n**通俗比喻**：住酒店。一切服务全包，你只负责使用。\n\n**常见产品**：钉钉、企业微信、OA系统、CRM、在线网盘、SaaS收银系统\n\n**特点**：零开发、零运维、自由度最低、开箱即用。\n\n### 4\\. 三层模型终极对比表（面试必背）\n\n|层级|全称|管控范围|运维成本|自由度|典型场景|\n|---|---|---|---|---|---|\n|**IaaS**|基础设施即服务|只管硬件，其余自己来|极高|极高|传统服务器、虚拟机部署|\n|**PaaS**|平台即服务|硬件\\+环境\\+中间件托管|低|中等|云原生、容器微服务|\n|**SaaS**|软件即服务|全套软件托管|几乎为0|极低|通用办公、商用软件|\n\n## 二、云原生（Cloud Native）完整概念\n\n**定义**：云原生不是技术，是**一套适配云计算的开发、部署、运维架构思想**。旨在让应用**天生适配云环境，弹性、高可用、可迭代、可运维**。\n\n**云原生四大核心支柱**（业界标准）：\n\n1. **容器化**：Docker 打包应用，环境一致、跨平台、秒级部署\n\n2. **编排调度**：K8s 管理容器，自动扩缩容、自愈、滚动更新\n\n3. **微服务**：单体拆分为独立小服务，独立开发、独立部署、独立扩容\n\n4. **服务网格**：统一治理微服务流量、熔断、限流、监控、链路追踪\n\n**核心价值**：\n\n- 彻底摆脱传统虚拟机笨重部署模式\n\n- 业务秒级发布、故障自愈、弹性伸缩\n\n- 适配海量并发、快速迭代的互联网业务\n\n**层级关系**：**云原生必须基于 PaaS 层实现**，IaaS太底层、SaaS太上层，均无法落地云原生架构。\n\n## 三、服务网格（Service Mesh）深度详解\n\n### 1\\. 是什么？\n\n**服务网格**：是**云原生微服务的专用基础设施层**，专门用来统一治理微服务之间的网络通信，**无侵入、零代码**实现服务治理。\n\n**核心定位**：把微服务的「流量治理能力」从业务代码中剥离出来，单独成为一层基础设施。\n\n### 2\\. 解决了什么问题？\n\n传统微服务（SpringCloud）痛点：**治理逻辑耦合业务代码**，熔断、限流、重试、负载均衡全部写在代码里，升级改造需要改代码、重启服务。\n\n服务网格实现：**业务只管业务，网格只管通信治理**。\n\n### 3\\. 经典架构：数据面 \\+ 控制面\n\n- **数据面（Sidecar）**：每个服务旁挂载一个代理容器（Envoy），接管所有进出流量，执行限流、熔断、重试、灰度、超时、监控\n\n- **控制面**：统一下发规则、配置管理，不处理流量，只负责调度管控（代表：Istio）\n\n### 4\\. 核心能力\n\n- 无侵入流量治理、动态灰度发布、蓝绿发布\n\n- 智能负载均衡、故障熔断、超时重试\n\n- 全链路监控、链路追踪、日志收集\n\n- 安全加密、服务认证、权限管控\n\n### 5\\. 主流框架\n\n**Istio**（业界标准）、Linkerd\n\n## 四、五者完整层级关系（终极串联）\n\n**底层基础**：IaaS（服务器、网络、硬件资源）\n\n**平台层**：PaaS（容器、K8s、运行环境，云原生底座）\n\n**架构模式**：云原生（容器\\+微服务\\+自动化运维的整套思想）\n\n**治理组件**：服务网格（云原生微服务的流量治理基础设施）\n\n**上层应用**：SaaS（最终交付的云上软件）\n\n## 五、面试极简背诵版\n\n1. **IaaS**：租虚拟机，管硬件，系统代码自己维护，自由度高、运维重。\n\n2. **PaaS**：托管运行环境，专注写业务代码，云原生架构的底层平台。\n\n3. **SaaS**：成品软件直接用，零开发零运维，自由度最低。\n\n4. **云原生**：基于PaaS\u002F容器的现代化架构，特点是容器化、微服务、弹性、自愈、快速迭代。\n\n5. **服务网格**：云原生微服务专用治理层，无代码侵入，统一管控流量、熔断、灰度、监控。","markdown",2677,{"frontmatter":42,"meta":43,"nodes":94},{},{"title":44,"description":45,"toc":46},"IaaS \u002F PaaS \u002F SaaS + 云原生 + 服务网格 全套通俗详解","这五个概念是云计算 & 云原生体系的地基：IaaS、PaaS、SaaS 是云计算三层交付模型（管「谁负责运维什么」）；云原生是上云的开发架构理念；服务网格是云原生微服务的专属治理架构。本文全程通俗、无废话、面试商用全覆盖。",{"title":4,"searchDepth":47,"depth":47,"links":48},5,[49,67,70,89,91],{"id":50,"depth":51,"text":52,"children":53},"iaaspaassaas",2,"一、云计算三层模型：IaaS、PaaS、SaaS（核心分层）",[54,58,61,64],{"id":55,"depth":56,"text":57},"iaaspaassaas-_1-iaas-infrastructure",3,"1. IaaS 基础设施即服务（Infrastructure）",{"id":59,"depth":56,"text":60},"iaaspaassaas-_2-paas-platform","2. PaaS 平台即服务（Platform）",{"id":62,"depth":56,"text":63},"iaaspaassaas-_3-saas-software","3. SaaS 软件即服务（Software）",{"id":65,"depth":56,"text":66},"iaaspaassaas-_4","4. 三层模型终极对比表（面试必背）",{"id":68,"depth":51,"text":69},"cloud-native","二、云原生（Cloud Native）完整概念",{"id":71,"depth":51,"text":72,"children":73},"service-mesh","三、服务网格（Service Mesh）深度详解",[74,77,80,83,86],{"id":75,"depth":56,"text":76},"service-mesh-_1","1. 是什么？",{"id":78,"depth":56,"text":79},"service-mesh-_2","2. 解决了什么问题？",{"id":81,"depth":56,"text":82},"service-mesh-_3","3. 经典架构：数据面 + 控制面",{"id":84,"depth":56,"text":85},"service-mesh-_4","4. 核心能力",{"id":87,"depth":56,"text":88},"service-mesh-_5","5. 主流框架",{"id":4,"depth":51,"text":90},"四、五者完整层级关系（终极串联）",{"id":92,"depth":51,"text":93},"-1","五、面试极简背诵版",[95,99,116,119,126,129,139,145,151,161,167,173,179,181,189,194,198,206,211,216,224,226,235,240,244,252,257,262,267,269,366,368,380,386,413,418,429,438,440,442,455,461,463,470,476,478,492,494,508,510,516,518,524,530,536,542,548,550],[96,97,44],"h1",{"id":98},"iaas-paas-saas",[100,101,102,103,107,108,111,112,115],"p",{},"这五个概念是",[104,105,106],"strong",{},"云计算 & 云原生体系的地基","：IaaS、PaaS、SaaS 是云计算三层交付模型（管「谁负责运维什么」）；云原生是",[104,109,110],{},"上云的开发架构理念","；服务网格是",[104,113,114],{},"云原生微服务的专属治理架构","。本文全程通俗、无废话、面试商用全覆盖。",[117,118,52],"h2",{"id":50},[100,120,121,122,125],{},"核心判断口诀：",[104,123,124],{},"从上到下，厂商管得越来越多，开发者管得越来越少","。",[127,128,57],"h3",{"id":55},[100,130,131,134,135,138],{},[104,132,133],{},"定义","：云厂商帮你搞定",[104,136,137],{},"底层硬件基础设施","，你自己管系统、软件、代码。",[100,140,141,144],{},[104,142,143],{},"交付内容","：虚拟机、服务器、磁盘、网络、负载均衡、带宽、IP。",[100,146,147,150],{},[104,148,149],{},"谁运维什么","：",[152,153,154,158],"ul",{},[155,156,157],"li",{},"厂商：硬件、机房、电力、物理网络",[155,159,160],{},"用户：操作系统、中间件、数据库、代码、部署运维",[100,162,163,166],{},[104,164,165],{},"通俗比喻","：租毛坯房。房子水电物业房东搞定，装修、家具、布置全部自己来。",[100,168,169,172],{},[104,170,171],{},"常见产品","：阿里云ECS、腾讯云CVM、AWS EC2、虚拟机、私有服务器",[100,174,175,178],{},[104,176,177],{},"特点","：最灵活、自由度最高、运维成本最大。",[127,180,60],{"id":59},[100,182,183,134,185,188],{},[104,184,133],{},[104,186,187],{},"基础设施 + 运行平台","，开发者只需要写代码、部署代码。",[100,190,191,193],{},[104,192,143],{},"：容器环境、JDK、Tomcat、数据库、缓存、消息队列、开发运行平台。",[100,195,196,150],{},[104,197,149],{},[152,199,200,203],{},[155,201,202],{},"厂商：硬件、系统、中间件、数据库、运行环境、扩容基础能力",[155,204,205],{},"用户：仅负责业务代码开发、业务配置",[100,207,208,210],{},[104,209,165],{},"：租精装公寓。房子装修家电齐全，你只需要拎包入住、布置自己的物品（写业务）。",[100,212,213,215],{},[104,214,171],{},"：K8s平台、阿里云SAE、腾讯云TCB、Redis云服务、MySQL云数据库",[100,217,218,220,221,125],{},[104,219,177],{},"：解放运维，专注业务，是",[104,222,223],{},"云原生核心依赖层",[127,225,63],{"id":62},[100,227,228,230,231,234],{},[104,229,133],{},"：云厂商直接交付",[104,232,233],{},"成品软件","，用户无需开发、无需部署、无需运维，直接开箱即用。",[100,236,237,239],{},[104,238,143],{},"：完整的在线软件、业务系统。",[100,241,242,150],{},[104,243,149],{},[152,245,246,249],{},[155,247,248],{},"厂商：底层全部运维、更新、扩容、故障修复",[155,250,251],{},"用户：仅使用软件功能、配置业务参数",[100,253,254,256],{},[104,255,165],{},"：住酒店。一切服务全包，你只负责使用。",[100,258,259,261],{},[104,260,171],{},"：钉钉、企业微信、OA系统、CRM、在线网盘、SaaS收银系统",[100,263,264,266],{},[104,265,177],{},"：零开发、零运维、自由度最低、开箱即用。",[127,268,66],{"id":65},[270,271,272,297],"table",{},[273,274,275],"thead",{},[276,277,278,282,285,288,291,294],"tr",{},[279,280,281],"th",{},"层级",[279,283,284],{},"全称",[279,286,287],{},"管控范围",[279,289,290],{},"运维成本",[279,292,293],{},"自由度",[279,295,296],{},"典型场景",[298,299,300,322,344],"tbody",{},[276,301,302,308,311,314,317,319],{},[303,304,305],"td",{},[104,306,307],{},"IaaS",[303,309,310],{},"基础设施即服务",[303,312,313],{},"只管硬件，其余自己来",[303,315,316],{},"极高",[303,318,316],{},[303,320,321],{},"传统服务器、虚拟机部署",[276,323,324,329,332,335,338,341],{},[303,325,326],{},[104,327,328],{},"PaaS",[303,330,331],{},"平台即服务",[303,333,334],{},"硬件+环境+中间件托管",[303,336,337],{},"低",[303,339,340],{},"中等",[303,342,343],{},"云原生、容器微服务",[276,345,346,351,354,357,360,363],{},[303,347,348],{},[104,349,350],{},"SaaS",[303,352,353],{},"软件即服务",[303,355,356],{},"全套软件托管",[303,358,359],{},"几乎为0",[303,361,362],{},"极低",[303,364,365],{},"通用办公、商用软件",[117,367,69],{"id":68},[100,369,370,372,373,376,377,125],{},[104,371,133],{},"：云原生不是技术，是",[104,374,375],{},"一套适配云计算的开发、部署、运维架构思想","。旨在让应用",[104,378,379],{},"天生适配云环境，弹性、高可用、可迭代、可运维",[100,381,382,385],{},[104,383,384],{},"云原生四大核心支柱","（业界标准）：",[387,388,389,395,401,407],"ol",{},[155,390,391,394],{},[104,392,393],{},"容器化","：Docker 打包应用，环境一致、跨平台、秒级部署",[155,396,397,400],{},[104,398,399],{},"编排调度","：K8s 管理容器，自动扩缩容、自愈、滚动更新",[155,402,403,406],{},[104,404,405],{},"微服务","：单体拆分为独立小服务，独立开发、独立部署、独立扩容",[155,408,409,412],{},[104,410,411],{},"服务网格","：统一治理微服务流量、熔断、限流、监控、链路追踪",[100,414,415,150],{},[104,416,417],{},"核心价值",[152,419,420,423,426],{},[155,421,422],{},"彻底摆脱传统虚拟机笨重部署模式",[155,424,425],{},"业务秒级发布、故障自愈、弹性伸缩",[155,427,428],{},"适配海量并发、快速迭代的互联网业务",[100,430,431,150,434,437],{},[104,432,433],{},"层级关系",[104,435,436],{},"云原生必须基于 PaaS 层实现","，IaaS太底层、SaaS太上层，均无法落地云原生架构。",[117,439,72],{"id":71},[127,441,76],{"id":75},[100,443,444,446,447,450,451,454],{},[104,445,411],{},"：是",[104,448,449],{},"云原生微服务的专用基础设施层","，专门用来统一治理微服务之间的网络通信，",[104,452,453],{},"无侵入、零代码","实现服务治理。",[100,456,457,460],{},[104,458,459],{},"核心定位","：把微服务的「流量治理能力」从业务代码中剥离出来，单独成为一层基础设施。",[127,462,79],{"id":78},[100,464,465,466,469],{},"传统微服务（SpringCloud）痛点：",[104,467,468],{},"治理逻辑耦合业务代码","，熔断、限流、重试、负载均衡全部写在代码里，升级改造需要改代码、重启服务。",[100,471,472,473,125],{},"服务网格实现：",[104,474,475],{},"业务只管业务，网格只管通信治理",[127,477,82],{"id":81},[152,479,480,486],{},[155,481,482,485],{},[104,483,484],{},"数据面（Sidecar）","：每个服务旁挂载一个代理容器（Envoy），接管所有进出流量，执行限流、熔断、重试、灰度、超时、监控",[155,487,488,491],{},[104,489,490],{},"控制面","：统一下发规则、配置管理，不处理流量，只负责调度管控（代表：Istio）",[127,493,85],{"id":84},[152,495,496,499,502,505],{},[155,497,498],{},"无侵入流量治理、动态灰度发布、蓝绿发布",[155,500,501],{},"智能负载均衡、故障熔断、超时重试",[155,503,504],{},"全链路监控、链路追踪、日志收集",[155,506,507],{},"安全加密、服务认证、权限管控",[127,509,88],{"id":87},[100,511,512,515],{},[104,513,514],{},"Istio","（业界标准）、Linkerd",[117,517,90],{"id":4},[100,519,520,523],{},[104,521,522],{},"底层基础","：IaaS（服务器、网络、硬件资源）",[100,525,526,529],{},[104,527,528],{},"平台层","：PaaS（容器、K8s、运行环境，云原生底座）",[100,531,532,535],{},[104,533,534],{},"架构模式","：云原生（容器+微服务+自动化运维的整套思想）",[100,537,538,541],{},[104,539,540],{},"治理组件","：服务网格（云原生微服务的流量治理基础设施）",[100,543,544,547],{},[104,545,546],{},"上层应用","：SaaS（最终交付的云上软件）",[117,549,93],{"id":92},[387,551,552,557,562,567,573],{},[155,553,554,556],{},[104,555,307],{},"：租虚拟机，管硬件，系统代码自己维护，自由度高、运维重。",[155,558,559,561],{},[104,560,328],{},"：托管运行环境，专注写业务代码，云原生架构的底层平台。",[155,563,564,566],{},[104,565,350],{},"：成品软件直接用，零开发零运维，自由度最低。",[155,568,569,572],{},[104,570,571],{},"云原生","：基于PaaS\u002F容器的现代化架构，特点是容器化、微服务、弹性、自愈、快速迭代。",[155,574,575,577],{},[104,576,411],{},"：云原生微服务专用治理层，无代码侵入，统一管控流量、熔断、灰度、监控。"]