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