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