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