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