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