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