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