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