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