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