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