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