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