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