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