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