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