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