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