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