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