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