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