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