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