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