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