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