[{"data":1,"prerenderedAt":2074},["ShallowReactive",2],{"blog-\u002Fblog\u002Fcomparison\u002Frongqi-vs-xuniji":3,"blog-related-\u002Fblog\u002Fcomparison\u002Frongqi-vs-xuniji":494},{"id":4,"title":5,"author":6,"body":7,"category":467,"cover":468,"date":469,"description":470,"draft":471,"extension":472,"faq":473,"featured":471,"image":468,"keywords":483,"meta":485,"navigation":486,"path":487,"seo":488,"sitemap":489,"stem":490,"tags":491,"updated":469,"__hash__":493},"blog\u002Fblog\u002Fcomparison\u002Frongqi-vs-xuniji.md","容器和虚拟机有什么区别","HNREIS",{"type":8,"value":9,"toc":442},"minimark",[10,19,24,27,105,109,112,116,142,145,153,156,176,178,181,184,198,201,213,216,236,240,247,266,269,273,292,296,315,319,322,330,333,353,356,403,406,409,436],[11,12,13,14,18],"p",{},"容器和虚拟机是两种虚拟化，",[15,16,17],"strong",{},"现代云原生用容器。"," 这篇讲清区别。",[20,21,23],"h2",{"id":22},"容器-vs-虚拟机","容器 vs 虚拟机",[11,25,26],{},"容器和虚拟机都是\"虚拟化\"技术——在一台物理机上运行多个独立的\"虚拟环境\"。但它们的实现方式和特点差别很大。",[28,29,30,46],"table",{},[31,32,33],"thead",{},[34,35,36,40,43],"tr",{},[37,38,39],"th",{},"维度",[37,41,42],{},"容器",[37,44,45],{},"虚拟机",[47,48,49,61,72,83,94],"tbody",{},[34,50,51,55,58],{},[52,53,54],"td",{},"隔离",[52,56,57],{},"应用级",[52,59,60],{},"系统级",[34,62,63,66,69],{},[52,64,65],{},"重量",[52,67,68],{},"轻量",[52,70,71],{},"重",[34,73,74,77,80],{},[52,75,76],{},"启动",[52,78,79],{},"快",[52,81,82],{},"慢",[34,84,85,88,91],{},[52,86,87],{},"资源",[52,89,90],{},"省",[52,92,93],{},"多",[34,95,96,99,102],{},[52,97,98],{},"隔离强度",[52,100,101],{},"弱于VM",[52,103,104],{},"强",[20,106,108],{"id":107},"容器docker","容器（Docker）",[11,110,111],{},"容器是以 Docker 为代表的轻量级虚拟化技术，它把应用和依赖打包到一个\"容器\"里运行，容器之间共享宿主机的操作系统内核。",[113,114,115],"h3",{"id":115},"优势",[117,118,119,125,130,136],"ul",{},[120,121,122,124],"li",{},[15,123,68],{},"：一个容器通常只有几十 MB 到几百 MB，比虚拟机省资源得多。一台物理机能跑几十上百个容器，虚拟机可能只能跑几个。",[120,126,127,129],{},[15,128,79],{},"：容器启动是秒级的，因为不用启动完整操作系统；虚拟机启动要几分钟，因为要启动整个系统。",[120,131,132,135],{},[15,133,134],{},"一致","：开发环境、测试环境、生产环境用同一个容器镜像，保证了环境一致性，告别\"在我电脑上能跑\"的问题。",[120,137,138,141],{},[15,139,140],{},"密度高","：一台机跑多个容器，资源利用率高。",[113,143,144],{"id":144},"劣势",[117,146,147],{},[120,148,149,152],{},[15,150,151],{},"隔离弱于 VM（共享内核）","：所有容器共享宿主机内核，隔离性不如虚拟机。如果一个容器触发内核漏洞，理论上可能影响其他容器。",[113,154,155],{"id":155},"适合",[117,157,158,164,170],{},[120,159,160,163],{},[15,161,162],{},"现代应用\u002F微服务","：微服务架构里每个服务用一个容器，天然契合。",[120,165,166,169],{},[15,167,168],{},"云原生","：云原生应用的标准部署方式。",[120,171,172,175],{},[15,173,174],{},"应用部署","：绝大多数应用部署场景都适合用容器。",[20,177,45],{"id":45},[11,179,180],{},"虚拟机是传统的虚拟化技术，它在物理机上模拟出完整的硬件，每个虚拟机都运行一个完整的操作系统。",[113,182,115],{"id":183},"优势-1",[117,185,186,192],{},[120,187,188,191],{},[15,189,190],{},"隔离强","：每个虚拟机都有完整的操作系统，彼此完全隔离，一个虚拟机出问题不会影响其他虚拟机。",[120,193,194,197],{},[15,195,196],{},"可跑不同系统","：一台物理机上可以同时跑 Windows、Linux、macOS 虚拟机。",[113,199,144],{"id":200},"劣势-1",[117,202,203,208],{},[120,204,205,207],{},[15,206,71],{},"：每个虚拟机都要装完整操作系统，资源占用大。一台物理机能跑的虚拟机数量有限。",[120,209,210,212],{},[15,211,82],{},"：启动要几分钟，因为要启动整个操作系统。",[113,214,155],{"id":215},"适合-1",[117,217,218,224,230],{},[120,219,220,223],{},[15,221,222],{},"完整系统需求","：需要运行完整操作系统的场景。",[120,225,226,229],{},[15,227,228],{},"不同操作系统","：需要在一台机上跑不同操作系统的场景。",[120,231,232,235],{},[15,233,234],{},"强隔离","：对隔离性要求极高的场景（比如不同租户、不同安全等级）。",[20,237,239],{"id":238},"现代趋势容器","现代趋势：容器",[11,241,242,243,246],{},"行业趋势是",[15,244,245],{},"容器化","，原因很简单——容器轻量、高效、契合现代应用架构。",[117,248,249,254,260],{},[120,250,251,253],{},[15,252,168],{},"：容器（Docker）+ 编排（Kubernetes，简称 K8s）是云原生的标准技术栈。",[120,255,256,259],{},[15,257,258],{},"微服务部署","：微服务架构的每个服务用容器部署，独立扩展、独立升级。",[120,261,262,265],{},[15,263,264],{},"高效利用资源","：容器的密度高，同样一台物理机能跑更多应用，硬件利用率高。",[20,267,268],{"id":268},"应用",[113,270,272],{"id":271},"_1-容器主流","1. 容器（主流）",[117,274,275,281,287],{},[120,276,277,280],{},[15,278,279],{},"应用\u002F微服务部署","：现代应用的标准部署方式。",[120,282,283,286],{},[15,284,285],{},"DevOps（CI\u002FCD）","：CI\u002FCD 流水线里用容器保证环境一致性。",[120,288,289,291],{},[15,290,168],{},"：云原生应用的基石。",[113,293,295],{"id":294},"_2-虚拟机","2. 虚拟机",[117,297,298,304,310],{},[120,299,300,303],{},[15,301,302],{},"云服务器（基础）","：阿里云 ECS、AWS EC2 本质都是虚拟机，云服务商用它做资源划分。",[120,305,306,309],{},[15,307,308],{},"完整系统","：需要完整操作系统的场景。",[120,311,312,314],{},[15,313,234],{},"：对隔离要求高的场景。",[113,316,318],{"id":317},"_3-结合","3. 结合",[11,320,321],{},"实际中两者经常结合使用：",[117,323,324],{},[120,325,326,329],{},[15,327,328],{},"虚拟机做基础+容器跑应用","：云服务商提供虚拟机作为基础设施，用户在虚拟机里跑容器部署应用。这是最常见的部署模式。",[20,331,332],{"id":332},"别踩的坑",[117,334,335,341,347],{},[120,336,337,340],{},[15,338,339],{},"强隔离用容器","：对隔离要求极高的场景（比如多租户的 SaaS、不同安全等级的系统混跑），用容器可能隔离不够，应该用虚拟机。",[120,342,343,346],{},[15,344,345],{},"小项目用 K8s","：几个容器的小项目硬上 K8s，运维复杂度远超收益。小项目用 Docker Compose 就够了。",[120,348,349,352],{},[15,350,351],{},"容器不管安全","：以为容器天然安全，不做镜像扫描、权限控制、网络隔离，存在安全隐患。",[20,354,355],{"id":355},"成本参考",[28,357,358,371],{},[31,359,360],{},[34,361,362,365,368],{},[37,363,364],{},"方案",[37,366,367],{},"说明",[37,369,370],{},"成本",[47,372,373,383,393],{},[34,374,375,377,380],{},[52,376,42],{},[52,378,379],{},"Docker\u002FK8s",[52,381,382],{},"低（开源）+运维",[34,384,385,387,390],{},[52,386,45],{},[52,388,389],{},"云\u002F自建",[52,391,392],{},"按规格",[34,394,395,398,401],{},[52,396,397],{},"容器服务",[52,399,400],{},"云托管K8s",[52,402,392],{},[11,404,405],{},"Docker 和 K8s 都是开源的，软件本身免费，成本主要是运维人力。云厂商的托管 K8s（阿里云 ACK、AWS EKS）按节点收费，比自己运维更省心但费用不低。",[20,407,408],{"id":408},"怎么选",[410,411,412,418,424,430],"ol",{},[120,413,414,417],{},[15,415,416],{},"现代应用用容器","：绝大多数应用部署场景，容器是更好的选择。",[120,419,420,423],{},[15,421,422],{},"完整系统\u002F强隔离用虚拟机","：需要完整系统隔离的场景用虚拟机。",[120,425,426,429],{},[15,427,428],{},"可结合（VM+容器）","：虚拟机做基础设施，容器跑应用，两者结合。",[120,431,432,435],{},[15,433,434],{},"小项目别上 K8s（过度）","：小项目用 Docker Compose 就够了，K8s 的复杂度对小项目是负担。",[437,438,439],"blockquote",{},[11,440,441],{},"广州市汉诺雷斯（HNREIS）帮企业做容器化部署和云原生架构。把你的部署需求告诉我们，我们给出方案。",{"title":443,"searchDepth":444,"depth":444,"links":445},"",2,[446,447,453,458,459,464,465,466],{"id":22,"depth":444,"text":23},{"id":107,"depth":444,"text":108,"children":448},[449,451,452],{"id":115,"depth":450,"text":115},3,{"id":144,"depth":450,"text":144},{"id":155,"depth":450,"text":155},{"id":45,"depth":444,"text":45,"children":454},[455,456,457],{"id":183,"depth":450,"text":115},{"id":200,"depth":450,"text":144},{"id":215,"depth":450,"text":155},{"id":238,"depth":444,"text":239},{"id":268,"depth":444,"text":268,"children":460},[461,462,463],{"id":271,"depth":450,"text":272},{"id":294,"depth":450,"text":295},{"id":317,"depth":450,"text":318},{"id":332,"depth":444,"text":332},{"id":355,"depth":444,"text":355},{"id":408,"depth":444,"text":408},"comparison",null,"2025-06-03","容器（轻量）和虚拟机（重）是两种虚拟化，现代云原生用容器。本文讲清两者区别和企业选什么。",false,"md",[474,477,480],{"q":475,"a":476},"容器和虚拟机什么区别？","容器（如Docker）是应用级隔离，轻量、快、省资源（共享内核）；虚拟机是系统级隔离，重、慢、资源多（每个装完整系统）。现代云原生应用多用容器（轻量高效），虚拟机用于需要完整系统隔离的场景。",{"q":478,"a":479},"企业该用容器还是虚拟机？","看场景。现代应用\u002F微服务\u002F云原生用容器（轻量高效，K8s编排）；需要完整系统隔离\u002F运行不同操作系统用虚拟机。很多企业云上用虚拟机做基础，应用用容器。建议现代应用用容器。",{"q":481,"a":482},"容器比虚拟机安全吗？","各有特点。虚拟机隔离更强（完整系统隔离）；容器共享内核，隔离弱于虚拟机（但够大部分场景）。安全要看实施。容器生态成熟，规范使用安全可控。建议规范使用，高隔离要求用虚拟机。",[42,45,484,168],"Docker",{},true,"\u002Fblog\u002Fcomparison\u002Frongqi-vs-xuniji",{"title":5,"description":470},{"loc":487},"blog\u002Fcomparison\u002Frongqi-vs-xuniji",[42,45,492],"架构","JP7WbU4GVJr197fvk90w_fuXMJZIOdWDP9VB8In8xDg",[495,899,1317,1684],{"id":496,"title":497,"author":6,"body":498,"category":467,"cover":468,"date":872,"description":873,"draft":471,"extension":472,"faq":874,"featured":471,"image":468,"keywords":884,"meta":889,"navigation":486,"path":890,"seo":891,"sitemap":892,"stem":893,"tags":894,"updated":872,"__hash__":898},"blog\u002Fblog\u002Fcomparison\u002Fapi-jiekou-shiye.md","API、接口、集成这些词到底是什么意思",{"type":8,"value":499,"toc":852},[500,506,510,516,519,530,535,538,541,547,550,555,557,568,573,576,579,593,596,610,615,618,622,636,639,650,653,658,661,668,685,690,693,696,718,723,726,763,769,772,798,801,804,830,833,847],[11,501,502,503],{},"老板常被 API、接口、集成这些技术词绕晕。",[15,504,505],{},"这篇用大白话讲清，帮老板听懂技术沟通。",[20,507,509],{"id":508},"api-是什么大白话","API 是什么（大白话）",[11,511,512,515],{},[15,513,514],{},"API 是两个软件\"对话\"的通道","。",[11,517,518],{},"例子：",[117,520,521,524,527],{},[120,522,523],{},"你的小程序要查物流 → 通过物流公司 API 问\"单号到哪了\" → 物流系统回\"已签收\"。",[120,525,526],{},"你的官网要收款 → 通过支付 API 让客户付款 → 支付系统回\"付款成功\"。",[120,528,529],{},"你的系统要发短信 → 通过短信 API 发 → 短信平台发出去。",[11,531,532,515],{},[15,533,534],{},"API 让不同软件自动互通数据，不用人工搬",[11,536,537],{},"打个比方：API 像餐厅的\"服务员\"——你（小程序）告诉服务员（API）要什么，服务员告诉厨房（另一个系统），厨房做好端回来。你不用自己进厨房。",[20,539,540],{"id":540},"接口是什么",[11,542,543,546],{},[15,544,545],{},"接口就是 API","（同义词）。技术人员说\"做个接口\"\"对接接口\"，就是做 API 让系统互通。",[20,548,549],{"id":549},"集成是什么",[11,551,552,515],{},[15,553,554],{},"集成 = 把多个系统通过 API 连起来，数据自动流通",[11,556,518],{},[117,558,559,562,565],{},[120,560,561],{},"独立站 + ERP 集成：独立站订单自动进 ERP，ERP 库存自动同步独立站。",[120,563,564],{},"小程序 + CRM 集成：小程序客户数据自动进 CRM。",[120,566,567],{},"系统 + 支付集成：系统通过支付 API 收款。",[11,569,570,515],{},[15,571,572],{},"集成让数据自动流，替代人工搬数据",[20,574,575],{"id":575},"企业为什么要做接口集成",[113,577,578],{"id":578},"不集成的问题",[117,580,581,584,587,590],{},[120,582,583],{},"多个系统（独立站\u002FERP\u002FCRM\u002F物流），数据不通。",[120,585,586],{},"人工把数据从一个系统搬到另一个（累、易错）。",[120,588,589],{},"数据不同步（独立站卖了 ERP 库存没减，超卖）。",[120,591,592],{},"效率低。",[113,594,595],{"id":595},"集成的好处",[117,597,598,601,604,607],{},[120,599,600],{},"数据自动流通（订单\u002F库存\u002F客户自动同步）。",[120,602,603],{},"替代人工（省人力、避错）。",[120,605,606],{},"实时同步（不超卖、不漏单）。",[120,608,609],{},"数据统一（可分析）。",[11,611,612,515],{},[15,613,614],{},"系统越多，集成价值越大",[20,616,617],{"id":617},"常见的集成场景",[113,619,621],{"id":620},"电商独立站","电商\u002F独立站",[117,623,624,627,630,633],{},[120,625,626],{},"独立站 ↔ ERP（订单\u002F库存同步）。",[120,628,629],{},"独立站 ↔ 物流（发货\u002F追踪）。",[120,631,632],{},"独立站 ↔ 支付（收款）。",[120,634,635],{},"独立站 ↔ CRM（客户管理）。",[113,637,638],{"id":638},"企业内部",[117,640,641,644,647],{},[120,642,643],{},"系统 ↔ OA（审批\u002F通知）。",[120,645,646],{},"系统 ↔ 财务（对账\u002F开票）。",[120,648,649],{},"系统 ↔ 企微\u002F钉钉（消息\u002F工作流）。",[113,651,652],{"id":652},"数据",[117,654,655],{},[120,656,657],{},"系统 ↔ 数据分析（数据汇总\u002F报表）。",[20,659,660],{"id":660},"集成怎么实现",[11,662,663,664,667],{},"通过 ",[15,665,666],{},"API 对接","：",[410,669,670,673,676,679,682],{},[120,671,672],{},"确认要对接的系统（ERP\u002F物流\u002F支付）。",[120,674,675],{},"看各系统是否提供 API（文档）。",[120,677,678],{},"开发对接（系统间调 API 传数据）。",[120,680,681],{},"测试（数据准确、异常处理）。",[120,683,684],{},"上线 + 监控。",[11,686,687,515],{},[15,688,689],{},"自建系统（Nuxt\u002FVue）能灵活对接任意系统，这是它比 SaaS 的优势",[20,691,692],{"id":692},"老板该懂什么",[11,694,695],{},"老板不用懂代码，懂这些：",[117,697,698,703,708,713],{},[120,699,700,515],{},[15,701,702],{},"API = 软件之间自动传数据的通道",[120,704,705,515],{},[15,706,707],{},"集成 = 多系统数据自动流通",[120,709,710,515],{},[15,711,712],{},"集成能替代人工、提效避错",[120,714,715,515],{},[15,716,717],{},"集成成本看系统数量和复杂度",[11,719,720,515],{},[15,721,722],{},"懂这些，就能和技术\u002F服务商沟通集成需求",[20,724,725],{"id":725},"集成的成本",[28,727,728,737],{},[31,729,730],{},[34,731,732,735],{},[37,733,734],{},"集成类型",[37,736,370],{},[47,738,739,747,755],{},[34,740,741,744],{},[52,742,743],{},"对接一个系统（如 ERP）",[52,745,746],{},"1-3 万",[34,748,749,752],{},[52,750,751],{},"多系统集成",[52,753,754],{},"3-8 万",[34,756,757,760],{},[52,758,759],{},"复杂（双向同步\u002F多系统\u002F定制）",[52,761,762],{},"8 万+",[11,764,765,768],{},[15,766,767],{},"ROI 明确","（替代人工、提效、避错）。",[20,770,771],{"id":771},"常见误区",[117,773,774,780,786,792],{},[120,775,776,779],{},[15,777,778],{},"\"接口很复杂不用懂\"","：老板懂概念就行（API = 数据通道）。",[120,781,782,785],{},[15,783,784],{},"\"不集成也能用\"","：人工搬数据累易错，不可持续。",[120,787,788,791],{},[15,789,790],{},"\"集成是一次性的\"","：系统升级\u002F业务变化，集成要维护。",[120,793,794,797],{},[15,795,796],{},"\"SaaS 不用集成\"","：SaaS 也要和其他系统打通。",[20,799,800],{"id":800},"怎么判断要不要集成",[11,802,803],{},"问自己：",[410,805,806,812,818,824],{},[120,807,808,811],{},[15,809,810],{},"有多个系统吗？"," 有 → 可能要集成。",[120,813,814,817],{},[15,815,816],{},"人工搬数据吗？"," 搬 → 该集成。",[120,819,820,823],{},[15,821,822],{},"数据需要同步吗？"," 需要 → 集成。",[120,825,826,829],{},[15,827,828],{},"集成 ROI 划算吗？","（省的人力 > 投入）划算 → 做。",[20,831,832],{"id":832},"怎么做",[410,834,835,838,841,844],{},[120,836,837],{},"梳理要对接的系统 + 数据流。",[120,839,840],{},"确认各系统 API。",[120,842,843],{},"开发对接。",[120,845,846],{},"测试 + 监控。",[437,848,849],{},[11,850,851],{},"广州市汉诺雷斯（HNREIS）提供系统集成（API 对接 ERP\u002F物流\u002F支付\u002FCRM），帮企业打通数据。把你的系统情况告诉我们，我们设计集成方案。",{"title":443,"searchDepth":444,"depth":444,"links":853},[854,855,856,857,861,866,867,868,869,870,871],{"id":508,"depth":444,"text":509},{"id":540,"depth":444,"text":540},{"id":549,"depth":444,"text":549},{"id":575,"depth":444,"text":575,"children":858},[859,860],{"id":578,"depth":450,"text":578},{"id":595,"depth":450,"text":595},{"id":617,"depth":444,"text":617,"children":862},[863,864,865],{"id":620,"depth":450,"text":621},{"id":638,"depth":450,"text":638},{"id":652,"depth":450,"text":652},{"id":660,"depth":444,"text":660},{"id":692,"depth":444,"text":692},{"id":725,"depth":444,"text":725},{"id":771,"depth":444,"text":771},{"id":800,"depth":444,"text":800},{"id":832,"depth":444,"text":832},"2024-05-15","老板常被 API、接口、集成这些技术词绕晕。本文用大白话讲清这些概念和企业集成场景，帮老板听懂技术沟通。",[875,878,881],{"q":876,"a":877},"API 到底是什么，大白话说？","API 是两个软件\"对话\"的通道。比如你的小程序要查物流，就通过物流公司的 API 问\"这个单号到哪了\"，物流系统通过 API 回\"已签收\"。API 让不同软件能互通数据，不用人工搬。你不用懂代码，只要知道\"API = 软件之间自动传数据的通道\"。",{"q":879,"a":880},"我们为什么要做接口集成？","因为你的多个系统要互通。比如独立站订单要进 ERP、库存要同步、物流要追踪，不集成就要人工把数据从一个系统搬到另一个（累、易错）。集成后数据自动流通，提效准确。系统越多，集成价值越大。",{"q":882,"a":883},"接口集成要多少钱？","看对接的系统数量和复杂度。对接一个系统（如 ERP）通常 1-3 万；多系统集成（ERP+物流+支付+CRM）3-8 万。集成能替代人工、提效避错，ROI 明确。",[885,886,887,888],"API接口通俗解释","什么是API","接口集成","系统对接",{},"\u002Fblog\u002Fcomparison\u002Fapi-jiekou-shiye",{"title":497,"description":873},{"loc":890},"blog\u002Fcomparison\u002Fapi-jiekou-shiye",[895,896,897],"API","概念","通俗","A7Jdt6jv4eTPYhdWviHOSLSzOR5pN0xxO_6QT9M2ODg",{"id":900,"title":901,"author":6,"body":902,"category":467,"cover":468,"date":1292,"description":1293,"draft":471,"extension":472,"faq":1294,"featured":471,"image":468,"keywords":1304,"meta":1309,"navigation":486,"path":1310,"seo":1311,"sitemap":1312,"stem":1313,"tags":1314,"updated":1292,"__hash__":1316},"blog\u002Fblog\u002Fcomparison\u002Fapi-wangguan-shi-shenme.md","API网关是什么",{"type":8,"value":903,"toc":1276},[904,911,914,917,920,930,933,936,942,946,960,964,978,982,996,1000,1014,1018,1032,1036,1044,1047,1093,1096,1100,1103,1148,1173,1175,1201,1203,1240,1243,1245,1271],[11,905,906,907,910],{},"API 网关是系统架构里常见的组件，",[15,908,909],{},"通俗说就是系统的\"统一前台\"。"," 这篇讲清是什么、解决什么、要不要用。",[20,912,901],{"id":913},"api网关是什么",[11,915,916],{},"在微服务架构里，后端可能拆分成几十个甚至上百个服务。如果每个服务都直接对外提供接口，客户端要记住每个服务的地址、每个服务都要自己处理鉴权限流——这会非常混乱。API 网关就是解决这个问题的。",[11,918,919],{},"所有外部请求先到网关，网关统一处理后转发到后端：",[921,922,927],"pre",{"className":923,"code":925,"language":926},[924],"language-text","客户端 → API网关（鉴权\u002F限流\u002F监控）→ 后端服务\n","text",[928,929,925],"code",{"__ignoreMap":443},[11,931,932],{},"类比公司前台：访客（客户端请求）先到前台登记（鉴权\u002F限流），前台再引导到对应部门（转发到后端服务）。访客不用记每个部门在哪，部门也不用自己设前台。",[20,934,935],{"id":935},"网关做什么",[11,937,938,939,515],{},"API 网关的核心职责是",[15,940,941],{},"把各服务都要做的\"公共事\"统一收口",[113,943,945],{"id":944},"_1-统一入口","1. 统一入口",[117,947,948,954],{},[120,949,950,953],{},[15,951,952],{},"所有请求统一入口","：客户端只需要知道网关地址，不用记每个服务的地址。",[120,955,956,959],{},[15,957,958],{},"后端服务不直接暴露","：后端服务可以部署在内网，只把网关暴露在外网，安全风险降低。",[113,961,963],{"id":962},"_2-鉴权","2. 鉴权",[117,965,966,972],{},[120,967,968,971],{},[15,969,970],{},"统一身份验证","：所有请求的鉴权在网关统一做，比如验证 token、校验权限。",[120,973,974,977],{},[15,975,976],{},"后端不用各自鉴权","：后端服务可以信任网关已通过的请求，专注业务逻辑，不用重复写鉴权代码。",[113,979,981],{"id":980},"_3-限流","3. 限流",[117,983,984,990],{},[120,985,986,989],{},[15,987,988],{},"防止过载和恶意请求","：网关按规则限制每个客户端、每个接口的调用频率，防止恶意刷接口或突发流量压垮后端。",[120,991,992,995],{},[15,993,994],{},"保护后端","：流量超出后端承受能力时，网关可以拒绝或排队，保护后端不被打挂。",[113,997,999],{"id":998},"_4-路由转发","4. 路由转发",[117,1001,1002,1008],{},[120,1003,1004,1007],{},[15,1005,1006],{},"请求转发到对应服务","：网关根据请求路径、头部等信息，把请求转发到正确的后端服务。",[120,1009,1010,1013],{},[15,1011,1012],{},"负载均衡","：一个服务有多个实例时，网关把请求分发到不同实例，提升整体处理能力。",[113,1015,1017],{"id":1016},"_5-监控日志","5. 监控日志",[117,1019,1020,1026],{},[120,1021,1022,1025],{},[15,1023,1024],{},"统一监控和日志","：所有请求的调用量、响应时间、错误率在网关统一采集，不用每个服务各自做。",[120,1027,1028,1031],{},[15,1029,1030],{},"可观测性","：网关的监控数据是排查问题、优化性能的重要依据。",[113,1033,1035],{"id":1034},"_6-协议转换","6. 协议转换",[117,1037,1038],{},[120,1039,1040,1043],{},[15,1041,1042],{},"不同协议转换","：客户端用 HTTP，后端用 gRPC 或 Dubbo，网关可以做协议转换，让前后端用各自适合的协议。",[20,1045,1046],{"id":1046},"为什么用网关",[28,1048,1049,1059],{},[31,1050,1051],{},[34,1052,1053,1056],{},[37,1054,1055],{},"问题",[37,1057,1058],{},"网关解决",[47,1060,1061,1069,1077,1085],{},[34,1062,1063,1066],{},[52,1064,1065],{},"鉴权散在各服务",[52,1067,1068],{},"统一鉴权",[34,1070,1071,1074],{},[52,1072,1073],{},"服务直接暴露",[52,1075,1076],{},"统一入口保护",[34,1078,1079,1082],{},[52,1080,1081],{},"流量过载",[52,1083,1084],{},"限流",[34,1086,1087,1090],{},[52,1088,1089],{},"监控散",[52,1091,1092],{},"统一监控",[11,1094,1095],{},"不用网关的情况下，每个服务都要自己实现鉴权、限流、监控、日志，代码重复、维护成本高，还容易出不一致的问题。网关把这些公共能力收口，后端服务可以更专注业务。",[20,1097,1099],{"id":1098},"用-vs-不用","用 vs 不用",[11,1101,1102],{},"网关不是所有系统都需要，要看规模和复杂度。",[28,1104,1105,1115],{},[31,1106,1107],{},[34,1108,1109,1112],{},[37,1110,1111],{},"情况",[37,1113,1114],{},"建议",[47,1116,1117,1125,1133,1141],{},[34,1118,1119,1122],{},[52,1120,1121],{},"服务少\u002F简单",[52,1123,1124],{},"不一定需要",[34,1126,1127,1130],{},[52,1128,1129],{},"微服务\u002F服务多",[52,1131,1132],{},"价值大",[34,1134,1135,1138],{},[52,1136,1137],{},"开放API",[52,1139,1140],{},"需要",[34,1142,1143,1146],{},[52,1144,1145],{},"多端接入",[52,1147,1140],{},[117,1149,1150,1156,1162,1168],{},[120,1151,1152,1155],{},[15,1153,1154],{},"服务少、简单","：比如一个单体应用就两三个接口，上不上网关差别不大，反而增加复杂度。",[120,1157,1158,1161],{},[15,1159,1160],{},"微服务、服务多","：服务一多，没有网关统一管理会很痛苦，网关价值就体现出来了。",[120,1163,1164,1167],{},[15,1165,1166],{},"开放 API","：对外提供 API 的场景，网关几乎是必需品——鉴权、限流、文档、监控都要在网关层做。",[120,1169,1170,1172],{},[15,1171,1145],{},"：APP、小程序、Web、第三方多端接入，网关统一入口能简化接入复杂度。",[20,1174,332],{"id":332},[117,1176,1177,1183,1189,1195],{},[120,1178,1179,1182],{},[15,1180,1181],{},"简单系统上重网关","：就两三个服务的简单系统，非要上 Kong 或 APISIX 这种重网关，属于过度设计，增加运维负担。",[120,1184,1185,1188],{},[15,1186,1187],{},"自己从头开发","：网关是成熟领域，有很多开源和商业产品（Kong、APISIX、云厂商网关），自己从头开发既慢又容易出问题。",[120,1190,1191,1194],{},[15,1192,1193],{},"网关成单点","：网关挂了整个系统就访问不了，必须做高可用部署（多实例、负载均衡）。",[120,1196,1197,1200],{},[15,1198,1199],{},"鉴权还散在各服务","：上了网关但鉴权还在各服务自己做，等于没用上网关的核心价值。",[20,1202,355],{"id":355},[28,1204,1205,1216],{},[31,1206,1207],{},[34,1208,1209,1211,1213],{},[37,1210,364],{},[37,1212,367],{},[37,1214,1215],{},"成本量级",[47,1217,1218,1229],{},[34,1219,1220,1223,1226],{},[52,1221,1222],{},"开源\u002F云网关",[52,1224,1225],{},"Kong\u002FAPISIX\u002F云厂商",[52,1227,1228],{},"低到中",[34,1230,1231,1234,1237],{},[52,1232,1233],{},"定制集成",[52,1235,1236],{},"和业务深度集成",[52,1238,1239],{},"中",[11,1241,1242],{},"主流网关产品（Kong、APISIX）开源免费，主要成本是部署运维。云厂商的网关服务（阿里云、腾讯云、AWS）按量计费，用量不大的话成本不高。自己定制集成成本中等，适合有特殊需求的场景。",[20,1244,408],{"id":408},[410,1246,1247,1253,1259,1265],{},[120,1248,1249,1252],{},[15,1250,1251],{},"评估服务数量和复杂度","：服务多、架构复杂才考虑网关。",[120,1254,1255,1258],{},[15,1256,1257],{},"简单系统不一定需要","：两三个服务的单体应用不用上网关。",[120,1260,1261,1264],{},[15,1262,1263],{},"微服务\u002F开放API用网关","：服务多、对外开放的场景，网关价值大。",[120,1266,1267,1270],{},[15,1268,1269],{},"优先成熟产品","：用 Kong、APISIX、云厂商网关，不要自己从头开发。",[437,1272,1273],{},[11,1274,1275],{},"广州市汉诺雷斯（HNREIS）帮企业做系统架构设计，含API网关选型和集成。把你的系统需求告诉我们，我们给出架构建议。",{"title":443,"searchDepth":444,"depth":444,"links":1277},[1278,1279,1287,1288,1289,1290,1291],{"id":913,"depth":444,"text":901},{"id":935,"depth":444,"text":935,"children":1280},[1281,1282,1283,1284,1285,1286],{"id":944,"depth":450,"text":945},{"id":962,"depth":450,"text":963},{"id":980,"depth":450,"text":981},{"id":998,"depth":450,"text":999},{"id":1016,"depth":450,"text":1017},{"id":1034,"depth":450,"text":1035},{"id":1046,"depth":444,"text":1046},{"id":1098,"depth":444,"text":1099},{"id":332,"depth":444,"text":332},{"id":355,"depth":444,"text":355},{"id":408,"depth":444,"text":408},"2024-05-28","API网关是系统的统一入口，负责转发、鉴权、限流和监控。本文用通俗方式讲清API网关是什么、解决什么问题、企业要不要用。",[1295,1298,1301],{"q":1296,"a":1297},"API网关是什么，简单说？","API网关是系统的\"统一前台\"——所有外部请求先到网关，网关再转发到后端服务。它统一处理鉴权、限流、监控、日志这些公共事，后端服务专注业务。类比公司前台，访客先到前台登记再进去。",{"q":1299,"a":1300},"企业一定要用API网关吗？","不一定。系统简单、服务少，不一定需要网关。服务多（微服务）、要统一鉴权限流监控、对外开放API、多端接入时，网关价值大。建议按规模和复杂度选，不要为用而用。",{"q":1302,"a":1303},"API网关要花多少钱？","看方式。用开源\u002F云网关产品（如Kong\u002FAPISIX\u002F云厂商网关）成本较低，按量或自建运维；定制集成成本中等。建议优先用成熟网关产品，而不是自己从头开发。",[1305,1306,1307,1308],"API网关","网关是什么","API管理","微服务网关",{},"\u002Fblog\u002Fcomparison\u002Fapi-wangguan-shi-shenme",{"title":901,"description":1293},{"loc":1310},"blog\u002Fcomparison\u002Fapi-wangguan-shi-shenme",[895,1315,492],"网关","CInYK4Or6VhknVKica8mjtvcuqr1CPVLRxjpJ0II3Fc",{"id":1318,"title":1319,"author":6,"body":1320,"category":467,"cover":468,"date":1660,"description":1661,"draft":471,"extension":472,"faq":1662,"featured":471,"image":468,"keywords":1672,"meta":1676,"navigation":486,"path":1677,"seo":1678,"sitemap":1679,"stem":1680,"tags":1681,"updated":1660,"__hash__":1683},"blog\u002Fblog\u002Fcomparison\u002Fbanben-kongzhi-git.md","代码版本控制（Git）是什么",{"type":8,"value":1321,"toc":1646},[1322,1329,1332,1336,1339,1345,1351,1357,1361,1365,1368,1378,1382,1385,1395,1399,1402,1416,1420,1430,1434,1503,1506,1509,1515,1521,1527,1533,1535,1553,1555,1558,1606,1609,1612,1638,1641],[11,1323,1324,1325,1328],{},"Git 是开发团队的必备工具，",[15,1326,1327],{},"通俗说是代码的\"时光机\"和\"协作台\"。"," 这篇讲清老板需要了解的。",[11,1330,1331],{},"软件开发是个高度协作的工作——几个甚至几十个开发同时改同一份代码，如果没有版本控制工具，光是\"谁改了什么\"\"怎么合并\"\"改坏了怎么回退\"这些问题就能让团队崩溃。Git 就是为了解决这些问题而生的工具，它已经成为软件开发行业的标准配置。这篇用通俗方式讲清 Git 是什么、为什么开发要用、老板需要关心什么。",[20,1333,1335],{"id":1334},"git是什么","Git是什么",[11,1337,1338],{},"Git 是代码版本控制工具，核心做三件事：",[11,1340,1341,1344],{},[15,1342,1343],{},"记录历史","——代码的每次改动都有记录（谁、什么时候、改了什么），能回到任何历史版本。相当于代码的\"时光机\"，改坏了随时回退。",[11,1346,1347,1350],{},[15,1348,1349],{},"多人协作","——多个开发同时改代码，Git 能自动合并、识别冲突。相当于代码的\"协作台\"，让团队并行开发而不互相踩踏。",[11,1352,1353,1356],{},[15,1354,1355],{},"分支","——从主线分出独立分支，在分支上做新功能，做完再合并回主线。相当于代码的\"平行宇宙\"，多个功能同时开发互不影响。",[20,1358,1360],{"id":1359},"为什么用git","为什么用Git",[113,1362,1364],{"id":1363},"_1-记录历史","1. 记录历史",[11,1366,1367],{},"代码的每一次改动（commit）都有完整记录——谁改的、什么时候改的、改了哪些文件、改了什么内容。这条记录链形成代码的完整历史。",[11,1369,1370,1373,1374,1377],{},[15,1371,1372],{},"改坏了能回退","——新功能改崩了，一条命令就能回到之前的稳定版本，不用从头再来。",[15,1375,1376],{},"知道谁改了什么","——出问题时能追溯到具体是哪次改动引入的 bug、谁改的，便于排查和复盘。历史记录还让代码审计、合规追溯成为可能——金融、医疗等强监管行业对代码变更有审计要求，Git 历史是天然的审计日志。",[113,1379,1381],{"id":1380},"_2-多人协作","2. 多人协作",[11,1383,1384],{},"没有版本控制时，多人改同一份代码要靠\"文件传来传去\"或\"共享文件夹\"，冲突频发、改动丢失、版本混乱。Git 让多人协作规范化——每个人在本地改，改完提交，Git 自动合并或识别冲突。",[11,1386,1387,1390,1391,1394],{},[15,1388,1389],{},"多人同时开发不冲突","——Git 的合并机制能自动合并不同部分的改动，相同部分的冲突会明确标出，让开发者手动解决。",[15,1392,1393],{},"合并代码规范","——通过 pull request（PR）或 merge request（MR）流程，代码合并前要经过 review（代码审查），保证质量。",[113,1396,1398],{"id":1397},"_3-分支","3. 分支",[11,1400,1401],{},"分支是 Git 的杀手级特性。从主线（main\u002Fmaster）分出独立分支，在分支上开发新功能，开发完成、测试通过后再合并回主线。",[11,1403,1404,1407,1408,1411,1412,1415],{},[15,1405,1406],{},"同时做多个功能","——开发 A 做支付功能、开发 B 做用户中心，两人各自在自己的分支上开发，互不影响。",[15,1409,1410],{},"互不影响","——某个功能开发中出了问题，不会污染主线，主线始终保持稳定。",[15,1413,1414],{},"测试稳定再合并","——功能在分支上开发测试，稳定后才合并到主线，主线始终是可发布的状态。",[113,1417,1419],{"id":1418},"_4-备份","4. 备份",[11,1421,1422,1425,1426,1429],{},[15,1423,1424],{},"代码在远程仓库备份","——本地代码 push 到远程仓库（GitHub、GitLab、Gitee），相当于异地备份。本地电脑坏了、丢了，代码还在远程仓库。",[15,1427,1428],{},"不怕丢","——多人协作时每个人都有一份完整副本，任何一份丢失都能从其他人恢复。",[20,1431,1433],{"id":1432},"git-vs-不用版本控制","Git vs 不用版本控制",[28,1435,1436,1448],{},[31,1437,1438],{},[34,1439,1440,1442,1445],{},[37,1441,39],{},[37,1443,1444],{},"Git",[37,1446,1447],{},"不用",[47,1449,1450,1461,1472,1483,1492],{},[34,1451,1452,1455,1458],{},[52,1453,1454],{},"历史",[52,1456,1457],{},"完整记录",[52,1459,1460],{},"没有",[34,1462,1463,1466,1469],{},[52,1464,1465],{},"协作",[52,1467,1468],{},"规范",[52,1470,1471],{},"手动易冲突",[34,1473,1474,1477,1480],{},[52,1475,1476],{},"回退",[52,1478,1479],{},"能",[52,1481,1482],{},"不能",[34,1484,1485,1487,1490],{},[52,1486,1355],{},[52,1488,1489],{},"支持",[52,1491,1460],{},[34,1493,1494,1497,1500],{},[52,1495,1496],{},"专业性",[52,1498,1499],{},"行业标准",[52,1501,1502],{},"不规范",[11,1504,1505],{},"不用版本控制的开发方式现在已经很少见——连个人开发者都用 Git 管理代码。如果一个开发团队不用 Git，基本可以判断为不规范。",[20,1507,1508],{"id":1508},"老板要了解的",[11,1510,1511,1514],{},[15,1512,1513],{},"规范团队都用 Git","——这是判断开发团队专业性的基本标准。用 Git 意味着团队有规范的开发流程（分支管理、代码审查、持续集成），而不是各自为政。反映专业性。",[11,1516,1517,1520],{},[15,1518,1519],{},"代码资产","——Git 仓库是企业的重要数字资产。仓库里不只是当前代码，还有完整的开发历史、设计决策、问题修复过程。这些是企业知识资产的重要组成部分。",[11,1522,1523,1526],{},[15,1524,1525],{},"源码交付","——服务商交付源码时，Git 仓库（含完整版本记录）是重要资产。只有当前代码没有历史记录，等于丢了开发过程的上下文。规范的源码交付应该包含 Git 仓库。源码含完整版本记录。",[11,1528,1529,1532],{},[15,1530,1531],{},"协作规范","——多人开发有据可查——谁做了什么、什么时候做的、为什么这么做，都有记录。出问题能追溯，避免推诿。",[20,1534,332],{"id":332},[11,1536,1537,1540,1541,1544,1545,1548,1549,1552],{},[15,1538,1539],{},"不用版本控制","——不规范、易丢代码。现在几乎没团队这么做了，但仍有个别服务商交付\"散落的代码文件\"而不是 Git 仓库，要注意。",[15,1542,1543],{},"不提交远程","——只在本地用 Git，不 push 到远程仓库，电脑坏了代码全丢。规范的团队都有远程仓库。",[15,1546,1547],{},"不分分支","——所有改动直接在主线做，功能混在一起乱、出问题难回退。规范团队都有分支策略（如 Git Flow、GitHub Flow）。",[15,1550,1551],{},"不写提交说明","——每次提交不写说明或写\"update\"\"fix\"这种无意义内容，不知道改了什么。规范团队要求写有意义的提交说明。",[20,1554,355],{"id":355},[11,1556,1557],{},"Git 本身免费（开源），成本在团队规范使用：",[28,1559,1560,1571],{},[31,1561,1562],{},[34,1563,1564,1567,1569],{},[37,1565,1566],{},"方面",[37,1568,367],{},[37,1570,370],{},[47,1572,1573,1584,1595],{},[34,1574,1575,1578,1581],{},[52,1576,1577],{},"Git工具",[52,1579,1580],{},"开源免费",[52,1582,1583],{},"免费",[34,1585,1586,1589,1592],{},[52,1587,1588],{},"托管平台",[52,1590,1591],{},"GitHub\u002FGitLab等",[52,1593,1594],{},"免费\u002F订阅",[34,1596,1597,1600,1603],{},[52,1598,1599],{},"团队规范",[52,1601,1602],{},"培训使用",[52,1604,1605],{},"低",[11,1607,1608],{},"Git 工具完全免费。托管平台有免费档（GitHub 公开仓库免费、GitLab 免费版）和付费档（私有仓库、企业版），按团队规模每月几美元到几十美元。团队规范使用要培训，但 Git 已经是开发行业基础技能，招聘时默认会，培训成本很低。",[20,1610,1611],{"id":1611},"怎么确认团队规范",[410,1613,1614,1620,1626,1632],{},[120,1615,1616,1619],{},[15,1617,1618],{},"确认团队用 Git 管理代码","——这是基本标准。问\"代码在哪个仓库\"\"分支策略是什么\"能快速判断。",[120,1621,1622,1625],{},[15,1623,1624],{},"代码在远程仓库（备份）","——有远程托管（GitHub、GitLab、Gitee 或自建），不只本地。",[120,1627,1628,1631],{},[15,1629,1630],{},"有分支和提交记录","——查看仓库历史，有没有规范的分支、有意义的提交说明、代码审查记录。",[120,1633,1634,1637],{},[15,1635,1636],{},"源码交付含 Git 仓库","——服务商交付时应该交付 Git 仓库（含完整历史），不只是当前代码文件。",[11,1639,1640],{},"按这几点核对，能快速判断开发团队是否规范。规范的 Git 使用是专业开发的基本标志，也是代码资产安全的基本保障。",[437,1642,1643],{},[11,1644,1645],{},"广州市汉诺雷斯（HNREIS）用Git规范管理代码，源码完整交付（含版本记录）。把你的项目需求告诉我们，我们规范交付。",{"title":443,"searchDepth":444,"depth":444,"links":1647},[1648,1649,1655,1656,1657,1658,1659],{"id":1334,"depth":444,"text":1335},{"id":1359,"depth":444,"text":1360,"children":1650},[1651,1652,1653,1654],{"id":1363,"depth":450,"text":1364},{"id":1380,"depth":450,"text":1381},{"id":1397,"depth":450,"text":1398},{"id":1418,"depth":450,"text":1419},{"id":1432,"depth":444,"text":1433},{"id":1508,"depth":444,"text":1508},{"id":332,"depth":444,"text":332},{"id":355,"depth":444,"text":355},{"id":1611,"depth":444,"text":1611},"2024-06-06","Git是代码版本控制工具，记录历史、支持协作和分支。本文用通俗方式讲清Git是什么、为什么开发要用、老板要了解什么。",[1663,1666,1669],{"q":1664,"a":1665},"Git是什么，简单说？","Git是代码版本控制工具，通俗说是代码的\"时光机\"和\"协作台\"——记录每次改动的历史（能回到任何版本）、多人同时改不冲突、支持分支（同时做多个功能）。开发团队用Git管理代码是行业标准。",{"q":1667,"a":1668},"老板为什么要了解Git？","Git关系到代码资产管理和交付。用Git意味着代码有完整历史、多人协作规范、源码可交付（有完整版本记录）。规范的开发团队都用Git，这反映团队专业性。源码交付时Git仓库是重要资产。",{"q":1670,"a":1671},"不用Git会怎样？","不用版本控制，代码改动没记录（改坏了回不去）、多人协作靠手动合并（易冲突丢代码）、没有分支（难同时做多功能）。现在专业开发都用Git，不用版本控制是不规范的表现。",[1444,1673,1674,1675],"版本控制","代码管理","代码版本",{},"\u002Fblog\u002Fcomparison\u002Fbanben-kongzhi-git",{"title":1319,"description":1661},{"loc":1677},"blog\u002Fcomparison\u002Fbanben-kongzhi-git",[1444,1673,1682],"开发","DDOY-P0lE1QLrLUQlE8ZQ8GpIAjcQnAG0lviW8QNo_I",{"id":1685,"title":1686,"author":6,"body":1687,"category":467,"cover":468,"date":2050,"description":2051,"draft":471,"extension":472,"faq":2052,"featured":471,"image":468,"keywords":2062,"meta":2065,"navigation":486,"path":2066,"seo":2067,"sitemap":2068,"stem":2069,"tags":2070,"updated":2050,"__hash__":2073},"blog\u002Fblog\u002Fcomparison\u002Fbendibu-vs-yunduan.md","本地部署和云部署的区别",{"type":8,"value":1688,"toc":2031},[1689,1696,1699,1703,1783,1785,1788,1790,1810,1812,1832,1834,1837,1839,1865,1867,1887,1889,1893,1904,1907,1918,1921,1929,1931,1957,1959,2006,2009,2026],[11,1690,1691,1692,1695],{},"软件部署在自己机房（本地）还是云上？",[15,1693,1694],{},"两者数据位置、成本、运维、弹性不同。"," 这篇讲清区别和选择。",[11,1697,1698],{},"很多企业在做信息化决策时，第一道选择题就是\"上云还是私有化部署\"。这件事看起来只是技术选型，实际上牵涉到数据归属、合规边界、运维投入、长期成本以及未来扩展性。如果一开始选错方向，后期再迁移会付出很大代价——数据迁移、接口改造、业务中断、人员重新培训。所以我们建议在动手之前，把两种方式的本质差异理清楚，再结合自身的数据敏感度、规模和运维能力做选择。",[20,1700,1702],{"id":1701},"本地部署-vs-云部署","本地部署 vs 云部署",[28,1704,1705,1717],{},[31,1706,1707],{},[34,1708,1709,1711,1714],{},[37,1710,39],{},[37,1712,1713],{},"本地部署",[37,1715,1716],{},"云部署",[47,1718,1719,1730,1741,1752,1763,1774],{},[34,1720,1721,1724,1727],{},[52,1722,1723],{},"数据位置",[52,1725,1726],{},"自己机房",[52,1728,1729],{},"云厂商",[34,1731,1732,1735,1738],{},[52,1733,1734],{},"可控性",[52,1736,1737],{},"高",[52,1739,1740],{},"依赖云厂商",[34,1742,1743,1746,1749],{},[52,1744,1745],{},"初期成本",[52,1747,1748],{},"高（买服务器）",[52,1750,1751],{},"低（按需付费）",[34,1753,1754,1757,1760],{},[52,1755,1756],{},"运维",[52,1758,1759],{},"自己负责",[52,1761,1762],{},"云厂商负责部分",[34,1764,1765,1768,1771],{},[52,1766,1767],{},"弹性",[52,1769,1770],{},"难（要买硬件）",[52,1772,1773],{},"强（随时扩容）",[34,1775,1776,1779,1781],{},[52,1777,1778],{},"上线速度",[52,1780,82],{},[52,1782,79],{},[20,1784,1713],{"id":1713},[11,1786,1787],{},"本地部署也叫私有化部署，是把软件连同数据库完整安装在客户自己机房的服务器上，所有数据从产生、存储到流转都在客户自己的硬件和网络环境里。云厂商或其他第三方无法直接访问到这些数据。",[113,1789,115],{"id":115},[117,1791,1792,1798,1804],{},[120,1793,1794,1797],{},[15,1795,1796],{},"数据自主","：数据完全在自己机房，物理上和网络上都可控，敏感行业（金融、政务、医疗、能源、核心商业数据）的合规要求通常通过本地部署满足。",[120,1799,1800,1803],{},[15,1801,1802],{},"完全可控","：不依赖云厂商，不会因为云厂商故障、停服、政策调整影响业务；网络策略、访问权限、加密方式都可以按自己的标准来制定。",[120,1805,1806,1809],{},[15,1807,1808],{},"长期固定成本","：初期一次性投入后，主要成本是电费、机房和运维人员工资，规模上来之后单位成本会被摊薄，长期运营相对划算。",[113,1811,144],{"id":144},[117,1813,1814,1820,1826],{},[120,1815,1816,1819],{},[15,1817,1818],{},"初期贵","：要买服务器、存储、网络设备，还要准备机房或机柜、UPS、空调、带宽等配套，光硬件投入就是几万到几十万，再加上软件授权和实施，初期门槛较高。",[120,1821,1822,1825],{},[15,1823,1824],{},"要运维","：硬件会坏、系统要打补丁、网络要排查、备份要做、安全要防护，需要专门的运维人员，小企业养一支运维团队成本不低。",[120,1827,1828,1831],{},[15,1829,1830],{},"弹性差","：业务量突然上涨，本地机房很难快速扩容——采购周期、上架、配置都要时间；业务量下降，已买的硬件也退不掉，资源闲置。",[20,1833,1716],{"id":1716},[11,1835,1836],{},"云部署是把软件部署在云厂商提供的服务器上（阿里云、腾讯云、华为云、AWS 等），按使用量付费。硬件、机房、网络、基础安全都由云厂商负责，客户只关注应用本身。",[113,1838,115],{"id":183},[117,1840,1841,1847,1853,1859],{},[120,1842,1843,1846],{},[15,1844,1845],{},"初期便宜","：按需付费，不用一次性买服务器，一台云主机从几十元到几百元每月起步，小企业或初创项目几乎零门槛。",[120,1848,1849,1852],{},[15,1850,1851],{},"省运维","：云厂商负责硬件、网络、机房、基础安全，客户只需要关注应用配置和数据，运维压力大幅下降，小团队也能跑稳生产环境。",[120,1854,1855,1858],{},[15,1856,1857],{},"弹性强","：业务高峰可以临时扩容（加机器、加带宽、加存储），低谷再缩容，按实际用量结算，特别适合季节性、活动型、流量波动大的业务。",[120,1860,1861,1864],{},[15,1862,1863],{},"上线快","：开通云主机几分钟，配合容器化部署可以做到当天开服、当天上线，对快速验证、敏捷迭代非常友好。",[113,1866,144],{"id":200},[117,1868,1869,1875,1881],{},[120,1870,1871,1874],{},[15,1872,1873],{},"数据在云","：数据物理上存在云厂商机房，依赖云厂商的安全能力和商业稳定性，敏感行业和强合规场景需要谨慎评估。",[120,1876,1877,1880],{},[15,1878,1879],{},"持续付费","：云资源按月或按年计费，长期累积下来可能比一次性买硬件更贵，规模越大、运行越久越明显。",[120,1882,1883,1886],{},[15,1884,1885],{},"合规限制","：部分行业（金融、政务、医疗、关键信息基础设施）的数据不允许上公有云，或只能上指定云、政务云、行业云。",[20,1888,408],{"id":408},[113,1890,1892],{"id":1891},"选本地私有化","选本地（私有化）",[117,1894,1895,1898,1901],{},[120,1896,1897],{},"数据高度敏感，比如金融交易、政务数据、医疗档案、核心商业数据、客户隐私。",[120,1899,1900],{},"要完全自主可控，对外部依赖、对供应商锁定特别敏感。",[120,1902,1903],{},"规模大、长期固定负载，本地部署的总账算下来比持续上云更划算。",[113,1905,1906],{"id":1906},"选云",[117,1908,1909,1912,1915],{},[120,1910,1911],{},"数据不敏感，或合规允许上云，希望轻装上阵。",[120,1913,1914],{},"业务有明显弹性，需要快速扩容、缩容，或处于快速验证阶段。",[120,1916,1917],{},"中小规模，没有专业的运维团队，希望把硬件和网络都外包出去。",[113,1919,1920],{"id":1920},"混合",[117,1922,1923,1926],{},[120,1924,1925],{},"敏感数据放本地（如核心交易、客户隐私），一般业务上云（如官网、营销、内部办公）。",[120,1927,1928],{},"通过专线、VPN、API 网关打通，做到\"敏感在内、弹性在外\"，是很多中大型企业的主流选择。",[20,1930,332],{"id":332},[117,1932,1933,1939,1945,1951],{},[120,1934,1935,1938],{},[15,1936,1937],{},"敏感数据上云","：忽视合规要求把不该上云的数据放公有云，可能面临监管处罚、整改甚至停业。",[120,1940,1941,1944],{},[15,1942,1943],{},"小规模本地部署","：业务量不大却硬上私有化，硬件折旧和运维成本根本摊不开，反而比上云贵。",[120,1946,1947,1950],{},[15,1948,1949],{},"只比单价不算总账","：云单价便宜不等于长期便宜，本地初期贵不等于长期贵，要按 3 年、5 年总成本（TCO）来算。",[120,1952,1953,1956],{},[15,1954,1955],{},"忽视云持续费用","：带宽、存储、CDN、增值服务都会按月累计，业务量起来后账单会快速上涨。",[20,1958,355],{"id":355},[28,1960,1961,1973],{},[31,1962,1963],{},[34,1964,1965,1968,1970],{},[37,1966,1967],{},"方式",[37,1969,367],{},[37,1971,1972],{},"成本特点",[47,1974,1975,1986,1997],{},[34,1976,1977,1980,1983],{},[52,1978,1979],{},"本地",[52,1981,1982],{},"服务器+机房+运维",[52,1984,1985],{},"初期高，长期固定",[34,1987,1988,1991,1994],{},[52,1989,1990],{},"云",[52,1992,1993],{},"按需付费",[52,1995,1996],{},"初期低，持续",[34,1998,1999,2001,2004],{},[52,2000,1920],{},[52,2002,2003],{},"敏感本地+一般云",[52,2005,1239],{},[20,2007,408],{"id":2008},"怎么选-1",[410,2010,2011,2014,2017,2020,2023],{},[120,2012,2013],{},"评估数据敏感度——是否涉及个人信息、重要数据、行业强合规。",[120,2015,2016],{},"评估规模和弹性需求——是稳定负载还是波动剧烈。",[120,2018,2019],{},"算总账（初期 + 长期 3-5 年），不只看月费。",[120,2021,2022],{},"评估运维能力——有没有专门的运维团队。",[120,2024,2025],{},"按需求选本地 \u002F 云 \u002F 混合，必要时分数据域分别部署。",[437,2027,2028],{},[11,2029,2030],{},"广州市汉诺雷斯（HNREIS）帮企业做部署方案，从云部署到本地私有化，按数据合规和成本需求选。把你的部署需求告诉我们，我们给出建议。",{"title":443,"searchDepth":444,"depth":444,"links":2032},[2033,2034,2038,2042,2047,2048,2049],{"id":1701,"depth":444,"text":1702},{"id":1713,"depth":444,"text":1713,"children":2035},[2036,2037],{"id":115,"depth":450,"text":115},{"id":144,"depth":450,"text":144},{"id":1716,"depth":444,"text":1716,"children":2039},[2040,2041],{"id":183,"depth":450,"text":115},{"id":200,"depth":450,"text":144},{"id":408,"depth":444,"text":408,"children":2043},[2044,2045,2046],{"id":1891,"depth":450,"text":1892},{"id":1906,"depth":450,"text":1906},{"id":1920,"depth":450,"text":1920},{"id":332,"depth":444,"text":332},{"id":355,"depth":444,"text":355},{"id":2008,"depth":444,"text":408},"2024-06-18","软件可以部署在自己机房（本地）或云上，两者数据、成本、运维和弹性不同。本文讲清本地部署和云部署的区别和选择。",[2053,2056,2059],{"q":2054,"a":2055},"本地部署和云部署什么区别？","本地部署是软件装在自己机房的服务器上，数据在自己手里，可控但要自己买服务器和维护；云部署是装在云服务器上（阿里云\u002F腾讯云等），不用买服务器、弹性扩容、按需付费，但数据在云厂商。核心区别在数据位置和运维责任。",{"q":2057,"a":2058},"企业该选本地还是云？","看数据敏感度和需求。数据高度敏感、要完全自主（金融\u002F政务\u002F核心商业数据），选本地（私有化）；要弹性、省运维、快速上线，选云。很多企业混合——敏感本地、一般云。建议按数据合规和成本需求选。",{"q":2060,"a":2061},"本地部署比云贵吗？","看规模。本地部署要一次性买服务器（几万到几十万）+持续电费机房运维，初期贵但量大后固定；云部署按需付费，初期便宜但长期持续付费，量大可能累积贵。要算总账，不是简单比单价。",[1713,1716,2063,2064],"部署方式","私有化部署",{},"\u002Fblog\u002Fcomparison\u002Fbendibu-vs-yunduan",{"title":1686,"description":2051},{"loc":2066},"blog\u002Fcomparison\u002Fbendibu-vs-yunduan",[2071,1990,2072],"部署","选型","2aw6C_2og_Eq04KLDnHPhU-NwU6cTqAJMhy_gQJj7tc",1781688908485]