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