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