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