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