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