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