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