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