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