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