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