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