[{"data":1,"prerenderedAt":681},["ShallowReactive",2],{"navigation_docs":3,"-web-dev-infrastructure-microservices-architecture-advantages":352,"-web-dev-infrastructure-microservices-architecture-advantages-surround":676},[4,54,83,116,125,161,179,200],{"title":5,"path":6,"stem":7,"children":8},"Ai","/ai","ai",[9,12,42,46,50],{"title":10,"path":6,"stem":11},"AI 技術探索","ai/index",{"title":13,"path":14,"stem":15,"children":16,"page":41},"Rag","/ai/rag","ai/RAG",[17,21,25,29,33,37],{"title":18,"path":19,"stem":20},"BM25 演算法深入解析：從 TF-IDF 到現代搜尋引擎的核心技術","/ai/rag/bm25-deep-dive-from-tf-idf-to-rag","ai/RAG/bm25-deep-dive-from-tf-idf-to-rag",{"title":22,"path":23,"stem":24},"Dense Retrieval（向量檢索）深入解析","/ai/rag/dense-retrieval-deep-dive","ai/RAG/dense-retrieval-deep-dive",{"title":26,"path":27,"stem":28},"RAG（Retrieval-Augmented Generation）原理與實作入門","/ai/rag/rag-intro-principles-and-implementation","ai/RAG/rag-intro-principles-and-implementation",{"title":30,"path":31,"stem":32},"RAG Retrieval Strategy 深入解析","/ai/rag/rag-retrieval-strategy-deep-dive","ai/RAG/rag-retrieval-strategy-deep-dive",{"title":34,"path":35,"stem":36},"Reciprocal Rank Fusion（RRF）教學：打造更穩定的檢索融合策略","/ai/rag/rrf-reciprocal-rank-fusion-guide","ai/RAG/rrf-reciprocal-rank-fusion-guide",{"title":38,"path":39,"stem":40},"TF-IDF（Term Frequency–Inverse Document Frequency）深入解析","/ai/rag/tf-idf-deep-dive","ai/RAG/tf-idf-deep-dive",false,{"title":43,"path":44,"stem":45},"Docus AI 功能完整實作指南","/ai/docus-ai-implementation","ai/docus-ai-implementation",{"title":47,"path":48,"stem":49},"llms.txt 是什麼？在 Nuxt 中控制 AI 與搜尋引擎爬蟲的新方式","/ai/llms-txt","ai/llms-txt",{"title":51,"path":52,"stem":53},"MCP（Model Context Protocol）是什麼？用「AI 的 USB-C」理解模型如何安全連接工具與資料","/ai/mcp_concept","ai/mcp_concept",{"title":55,"path":56,"stem":57,"children":58,"page":41},"Data Analysis","/data-analysis","data-analysis",[59,63,67,71,75,79],{"title":60,"path":61,"stem":62},"Exploratory Data Analysis（EDA）資料探索分析入門","/data-analysis/exploratory-data-analysis-eda","data-analysis/exploratory-data-analysis-eda",{"title":64,"path":65,"stem":66},"PR-AUC 深入解析：不平衡分類問題的重要評估指標","/data-analysis/pr-auc-for-imbalanced-classification","data-analysis/pr-auc-for-imbalanced-classification",{"title":68,"path":69,"stem":70},"ROC-AUC 深入解析：理解分類模型的判斷能力","/data-analysis/roc-auc-complete-guide","data-analysis/roc-auc-complete-guide",{"title":72,"path":73,"stem":74},"SHAP（SHapley Additive exPlanations）模型解釋方法深入解析","/data-analysis/shap-model-interpretation-complete-guide","data-analysis/shap-model-interpretation-complete-guide",{"title":76,"path":77,"stem":78},"Social Network Analysis（SNA）深入解析","/data-analysis/social-network-analysis-sna","data-analysis/social-network-analysis-sna",{"title":80,"path":81,"stem":82},"Time-based Split：為什麼時間序列資料不能使用 Random Split？","/data-analysis/time-based-split-vs-random-split","data-analysis/time-based-split-vs-random-split",{"title":84,"path":85,"stem":86,"children":87,"page":41},"MachineLearning","/machine_learning","machine_learning",[88,92,96,100,104,108,112],{"title":89,"path":90,"stem":91},"Confusion Matrix（混淆矩陣）完整解析","/machine_learning/confusion-matrix","machine_learning/confusion-matrix",{"title":93,"path":94,"stem":95},"Decision Tree 模型完整教學：從原理到 Python 實作","/machine_learning/decision-tree-complete-guide","machine_learning/decision-tree-complete-guide",{"title":97,"path":98,"stem":99},"為什麼 Decision Tree 在 Tabular Data 上常常勝過 Deep Learning？","/machine_learning/decision-tree-vs-deep-learning-on-tabular-data","machine_learning/decision-tree-vs-deep-learning-on-tabular-data",{"title":101,"path":102,"stem":103},"LightGBM 模型入門：理解高效能的 Gradient Boosting 演算法","/machine_learning/lightgbm-intro-for-tabular-data","machine_learning/lightgbm-intro-for-tabular-data",{"title":105,"path":106,"stem":107},"Logistic Regression（Logit 回歸）完整教學","/machine_learning/logistic-regression-complete-guide","machine_learning/logistic-regression-complete-guide",{"title":109,"path":110,"stem":111},"為什麼模型訓練需要 Train / Validation / Test Dataset？","/machine_learning/train-validation-test-dataset","machine_learning/train-validation-test-dataset",{"title":113,"path":114,"stem":115},"XGBoost 原理與實務教學","/machine_learning/xgboost-complete-guide","machine_learning/xgboost-complete-guide",{"title":117,"path":118,"stem":119,"children":120,"page":41},"Network","/network","network",[121],{"title":122,"path":123,"stem":124},"DNS 設定入門：CNAME vs A Record 完整解析","/network/dns-cname-vs-a-record-guide","network/dns-cname-vs-a-record-guide",{"title":126,"path":127,"stem":128,"children":129},"Nuxt","/nuxt","nuxt",[130,133,137,141,145,149,153,157],{"title":131,"path":127,"stem":132},"Nuxt 實戰指南","nuxt/index",{"title":134,"path":135,"stem":136},"Abstraction Layer 與 Adapter 的差別，一次搞懂設計角色","/nuxt/adapter_abstraction_layer","nuxt/adapter_abstraction_layer",{"title":138,"path":139,"stem":140},"Nuxt 4 全面理解 — 專案檔案結構解析","/nuxt/directory_structure","nuxt/directory_structure",{"title":142,"path":143,"stem":144},"Nuxt 前端 build 流程完整解析","/nuxt/frontend_build","nuxt/frontend_build",{"title":146,"path":147,"stem":148},"Nitro 是什麼？從 Nuxt 專案到 Server 與 Edge 的關鍵引擎","/nuxt/nitro","nuxt/nitro",{"title":150,"path":151,"stem":152},"深入理解 Nuxt 的 .nuxt 與 .output：為什麼部署時一定要分清楚？","/nuxt/nuxt_and_output","nuxt/nuxt_and_output",{"title":154,"path":155,"stem":156},"Nuxt 中 dev、build、preview 的差異一次搞懂","/nuxt/nuxt_dev_build_preview","nuxt/nuxt_dev_build_preview",{"title":158,"path":159,"stem":160},"Nuxt Image vs \u003Cimg>：為什麼 Nuxt 3 專案幾乎都該用 \u003CNuxtImg>？","/nuxt/nuxt_image","nuxt/nuxt_image",{"title":162,"path":163,"stem":164,"children":165},"Python 程式開發","/python","python/index",[166,167,171,175],{"title":162,"path":163,"stem":164},{"title":168,"path":169,"stem":170},"如何在 FastAPI 中調用記憶體 Buffer 回傳圖片 (附實例)","/python/memory_buffer","python/memory_buffer",{"title":172,"path":173,"stem":174},"Python 單元測試教學：如何為你的程式撰寫 Test","/python/python-unit-testing-unittest-pytest","python/python-unit-testing-unittest-pytest",{"title":176,"path":177,"stem":178},"如何使用 uv 取代 pip：改善 Python 專案的開發流程","/python/uv","python/uv",{"title":180,"path":181,"stem":182,"children":183,"page":41},"Statistic","/statistic","statistic",[184,188,192,196],{"title":185,"path":186,"stem":187},"卡方檢定（Chi-Square Test）入門教學","/statistic/chi-square-test-intro","statistic/chi-square-test-intro",{"title":189,"path":190,"stem":191},"常見抽樣方法（Sampling Methods）教學：Stratified、Quota、Convenience、Systematic、Simple Random","/statistic/common-sampling-methods-guide","statistic/common-sampling-methods-guide",{"title":193,"path":194,"stem":195},"Cramér’s V 指標介紹：如何衡量兩個類別變數之間的關聯","/statistic/cramers-v-for-categorical-association","statistic/cramers-v-for-categorical-association",{"title":197,"path":198,"stem":199},"Mann–Whitney U 與 Kolmogorov–Smirnov（KS）檢定：非參數統計檢定的入門指南","/statistic/mann-whitney-u-and-ks-test-intro","statistic/mann-whitney-u-and-ks-test-intro",{"title":201,"path":202,"stem":203,"children":204},"WebDev","/web_dev","web_dev",[205,208,234,248,282,312,334],{"title":206,"path":202,"stem":207},"Web 前端開發","web_dev/index",{"title":209,"path":210,"stem":211,"children":212},"瀏覽器與渲染","/web_dev/browser","web_dev/browser/index",[213,214,218,222,226,230],{"title":209,"path":210,"stem":211},{"title":215,"path":216,"stem":217},"瀏覽器儲存空間完整解析：Cookie、localStorage、IndexedDB 到 Cache Storage","/web_dev/browser/browser-storage-comprehensive-guide","web_dev/browser/browser-storage-comprehensive-guide",{"title":219,"path":220,"stem":221},"DOM (Document Object Model) 深入解析","/web_dev/browser/dom","web_dev/browser/dom",{"title":223,"path":224,"stem":225},"Service Worker Request Flow 深入解析","/web_dev/browser/service-worker-request-flow","web_dev/browser/service-worker-request-flow",{"title":227,"path":228,"stem":229},"CSR、SSR 與 SSG 是什麼？前端渲染策略完整比較","/web_dev/browser/ssr_csr_ssg","web_dev/browser/ssr_csr_ssg",{"title":231,"path":232,"stem":233},"Virtual DOM 深入解析：為什麼它能優化前端效能？","/web_dev/browser/virtual_dom","web_dev/browser/virtual_dom",{"title":235,"path":236,"stem":237,"children":238},"圖形技術","/web_dev/graphics","web_dev/graphics/index",[239,240,244],{"title":235,"path":236,"stem":237},{"title":241,"path":242,"stem":243},"為什麼 Three.js 專案幾乎都選擇 CSR？從 SSR 問題談起","/web_dev/graphics/threejs_csr","web_dev/graphics/threejs_csr",{"title":245,"path":246,"stem":247},"WebGL 是什麼？為什麼前端 3D 幾乎都靠它？","/web_dev/graphics/webgl","web_dev/graphics/webGL",{"title":249,"path":250,"stem":251,"children":252},"架構與配置","/web_dev/infrastructure","web_dev/infrastructure/index",[253,254,258,262,266,270,274,278],{"title":249,"path":250,"stem":251},{"title":255,"path":256,"stem":257},"Zeabur + K3s + Nuxt 部署架構完整解析","/web_dev/infrastructure/k3s-zeabur","web_dev/infrastructure/K3s-zeabur",{"title":259,"path":260,"stem":261},"ECS vs Docker vs Kubernetes：從部署堆疊理解三層架構","/web_dev/infrastructure/ecs-docker-kubernetes-stack","web_dev/infrastructure/ecs-docker-kubernetes-stack",{"title":263,"path":264,"stem":265},"ECS vs VPS 是什麼？從部署網站的角度一次搞懂差別","/web_dev/infrastructure/ecs-vs-vps","web_dev/infrastructure/ecs-vs-vps",{"title":267,"path":268,"stem":269},"Zeabur 內網服務連線完整入門指南","/web_dev/infrastructure/k3s-internal-networking","web_dev/infrastructure/k3s-internal-networking",{"title":271,"path":272,"stem":273},"使用 Microservices 架構設計系統的優勢解析","/web_dev/infrastructure/microservices-architecture-advantages","web_dev/infrastructure/microservices-architecture-advantages",{"title":275,"path":276,"stem":277},"Nginx 入門教學：從反向代理到與 Kubernetes 的架構比較","/web_dev/infrastructure/nginx-intro","web_dev/infrastructure/nginx-intro",{"title":279,"path":280,"stem":281},"YAML 配置是什麼？為什麼現代開發都在用它","/web_dev/infrastructure/yaml-configuration","web_dev/infrastructure/yaml-configuration",{"title":283,"path":284,"stem":285,"children":286},"網絡與通訊","/web_dev/network","web_dev/network/index",[287,288,292,296,300,304,308],{"title":283,"path":284,"stem":285},{"title":289,"path":290,"stem":291},"HTTP Request 結構完整解析：從 Request Line 到 Header 一次看懂","/web_dev/network/http-request-structure","web_dev/network/http-request-structure",{"title":293,"path":294,"stem":295},"OSI 模型（Open Systems Interconnection Model）完整解析","/web_dev/network/osi-model","web_dev/network/osi-model",{"title":297,"path":298,"stem":299},"RESTful API 設計原則與實務解析","/web_dev/network/restful-api","web_dev/network/restful-api",{"title":301,"path":302,"stem":303},"RESTful API 五大設計原則深入解析","/web_dev/network/restful-api-principles","web_dev/network/restful-api-principles",{"title":305,"path":306,"stem":307},"Server-Sent Events (SSE) 深入解析與實作教學","/web_dev/network/sse-introduction","web_dev/network/sse-introduction",{"title":309,"path":310,"stem":311},"WebSocket 入門教學：從概念到 Node.js 實作","/web_dev/network/websocket-introduction","web_dev/network/websocket-introduction",{"title":313,"path":314,"stem":315,"children":316},"認證與安全","/web_dev/security","web_dev/security/index",[317,318,322,326,330],{"title":313,"path":314,"stem":315},{"title":319,"path":320,"stem":321},"使用 Cookie 與 Session 建立使用者驗證（完整新手教學）","/web_dev/security/cookie-session-authentication","web_dev/security/cookie-session-authentication",{"title":323,"path":324,"stem":325},"JWT 驗證機制完整解析：從登入流程到實務應用","/web_dev/security/jwt-authentication","web_dev/security/jwt-authentication",{"title":327,"path":328,"stem":329},"Secret Key 簽名是什麼？從零理解資料簽名的本質","/web_dev/security/secret-key-signing","web_dev/security/secret-key-signing",{"title":331,"path":332,"stem":333},"SSH（Secure Shell）是什麼？從遠端登入到安全通道的核心概念","/web_dev/security/ssh","web_dev/security/ssh",{"title":335,"path":336,"stem":337,"children":338},"SEO 與規範","/web_dev/seo","web_dev/seo/index",[339,340,344,348],{"title":335,"path":336,"stem":337},{"title":341,"path":342,"stem":343},"Canonical URL 是什麼？用生活化方式搞懂前端 SEO 的基本保命符","/web_dev/seo/canonical_link","web_dev/seo/canonical_link",{"title":345,"path":346,"stem":347},"robots.txt 是什麼？SEO 的第一道守門員","/web_dev/seo/robot_txt","web_dev/seo/robot_txt",{"title":349,"path":350,"stem":351},"Nuxt SEO 中的 Meta 與 SEO 工具是如何運作的？","/web_dev/seo/seo","web_dev/seo/seo",{"id":353,"title":271,"body":354,"description":662,"extension":663,"links":664,"meta":665,"navigation":673,"path":272,"seo":674,"stem":273,"__hash__":675},"docs/web_dev/infrastructure/microservices-architecture-advantages.md",{"type":355,"value":356,"toc":647},"minimark",[357,362,366,369,372,375,379,387,390,406,409,412,423,426,428,432,435,437,441,444,447,461,464,466,470,473,476,490,493,501,503,507,510,513,533,536,538,542,545,548,559,561,565,568,571,585,588,590,594,597,599,603,607,610,612,616,619,633,636,638,641,644],[358,359,361],"h2",{"id":360},"從單體架構monolith開始理解","從單體架構（Monolith）開始理解",[363,364,365],"p",{},"在談 microservices 之前，我們先從最常見的「單體架構（Monolithic Architecture）」開始。",[363,367,368],{},"在單體架構中，整個系統會被寫成一個完整的應用程式。無論是使用者登入、訂單處理、支付流程，還是通知服務，全部都在同一個 codebase 中運作。這種設計在專案初期非常直覺，也容易開發與部署。",[363,370,371],{},"然而，當系統逐漸變大時，問題就會開始浮現。任何一個小改動，都可能影響整個系統；部署一次就必須整體更新；團隊之間的協作也容易互相干擾。這些限制，正是 microservices 架構誕生背後的動力。",[373,374],"hr",{},[358,376,378],{"id":377},"什麼是-microservices-架構","什麼是 Microservices 架構？",[380,381,382,386],"note",{},[383,384,385],"strong",{},"Microservices（微服務架構）"," 是一種將系統拆分為多個「小型、獨立服務」的設計方式。每一個服務專注於單一功能，並且可以獨立開發、部署與擴展。",[363,388,389],{},"例如，一個電商系統可以被拆成：",[391,392,393,397,400,403],"ul",{},[394,395,396],"li",{},"使用者服務（User Service）",[394,398,399],{},"商品服務（Product Service）",[394,401,402],{},"訂單服務（Order Service）",[394,404,405],{},"支付服務（Payment Service）",[363,407,408],{},"這些服務之間通常透過 HTTP API 或 message queue（例如 Kafka）來進行溝通，而不是直接呼叫內部 function。",[363,410,411],{},"從架構的角度來看，它會比較像這樣：",[413,414,419],"pre",{"className":415,"code":417,"language":418},[416],"language-text","Client\n  ↓\nAPI Gateway\n  ↓\n┌───────────────┬───────────────┬───────────────┐\n│ User Service  │ Order Service │ Payment Service│\n└───────────────┴───────────────┴───────────────┘\n","text",[420,421,417],"code",{"__ignoreMap":422},"",[363,424,425],{},"這種設計讓系統從「一個巨大應用」轉變為「多個協作的小系統」。",[373,427],{},[358,429,431],{"id":430},"為什麼要使用-microservices","為什麼要使用 Microservices？",[363,433,434],{},"接下來我們從幾個核心面向來理解 microservices 的優勢，而這些優勢通常會在系統規模變大後變得非常關鍵。",[373,436],{},[358,438,440],{"id":439},"一系統可以獨立擴展scalability","一、系統可以獨立擴展（Scalability）",[363,442,443],{},"在單體架構中，如果系統某一部分（例如訂單服務）流量暴增，你通常只能「整個系統一起擴展」。",[363,445,446],{},"但在 microservices 架構中，你可以只針對「需要的服務」進行擴展。例如：",[391,448,449,455],{},[394,450,451,454],{},[383,452,453],{},"訂單服務流量高"," → 只增加 Order Service 的 instances",[394,456,457,460],{},[383,458,459],{},"使用者服務穩定"," → 不需要額外資源",[363,462,463],{},"這種「細粒度擴展」可以有效降低成本，並提升資源使用效率。常搭配 Kubernetes 等容器編排平台來實作。",[373,465],{},[358,467,469],{"id":468},"二服務之間解耦decoupling","二、服務之間解耦（Decoupling）",[363,471,472],{},"Microservices 的核心精神之一是「高內聚、低耦合」。",[363,474,475],{},"每個服務只關心自己的業務邏輯，例如：",[391,477,478,484],{},[394,479,480,483],{},[383,481,482],{},"User Service"," 不需要知道 Payment 的內部實作。",[394,485,486,489],{},[383,487,488],{},"Order Service"," 只需要呼叫 Payment API，而不是直接操作其資料庫。",[363,491,492],{},"這樣的好處是：",[391,494,495,498],{},[394,496,497],{},"修改某個服務，不會影響其他服務。",[394,499,500],{},"可以降低系統的複雜度傳播（complexity propagation）。",[373,502],{},[358,504,506],{"id":505},"三可以使用不同技術棧polyglot-architecture","三、可以使用不同技術棧（Polyglot Architecture）",[363,508,509],{},"在單體架構中，你通常會被限制使用同一種語言與框架。",[363,511,512],{},"但在 microservices 架構中，每個服務可以根據需求選擇最適合的技術：",[391,514,515,521,527],{},[394,516,517,520],{},[383,518,519],{},"高併發 API"," → 使用 Go",[394,522,523,526],{},[383,524,525],{},"資料分析"," → 使用 Python",[394,528,529,532],{},[383,530,531],{},"即時通訊"," → 使用 Node.js",[363,534,535],{},"這種「技術多樣性」讓團隊可以針對不同問題選擇最佳解。",[373,537],{},[358,539,541],{"id":540},"四部署更靈活independent-deployment","四、部署更靈活（Independent Deployment）",[363,543,544],{},"在 microservices 架構中，每個服務都可以獨立部署。",[363,546,547],{},"這代表：",[391,549,550,553,556],{},[394,551,552],{},"修正 Payment bug，不需要重新部署整個系統。",[394,554,555],{},"可以針對單一服務做 rollback。",[394,557,558],{},"支援 CI/CD pipeline 的細粒度發布。",[373,560],{},[358,562,564],{"id":563},"五系統更具容錯能力fault-isolation","五、系統更具容錯能力（Fault Isolation）",[363,566,567],{},"在單體架構中，一個模組出錯，可能會導致整個系統崩潰。",[363,569,570],{},"但在 microservices 中：",[391,572,573,579],{},[394,574,575,578],{},[383,576,577],{},"Payment Service 掛掉"," → 不影響 User Service。",[394,580,581,584],{},[383,582,583],{},"某個 API timeout"," → 可以 fallback 或 retry。",[363,586,587],{},"這種「故障隔離（Fault Isolation）」讓系統更穩定，也更容易設計 resiliency 機制（如 circuit breaker）。",[373,589],{},[358,591,593],{"id":592},"六團隊可以並行開發team-scalability","六、團隊可以並行開發（Team Scalability）",[363,595,596],{},"當系統拆分成多個服務後，團隊也可以依照服務來分工。每個團隊可以獨立開發、獨立部署，並擁有自己的 release cycle。這會大幅提升開發效率，並降低跨團隊溝通成本。",[373,598],{},[358,600,602],{"id":601},"microservices-的代價","Microservices 的代價",[604,605,606],"warning",{},"雖然 microservices 有很多優勢，但它並不是「免費的」。你同時也需要面對分散式系統的複雜性、資料一致性問題（Eventual Consistency）以及監控與分散式追蹤（Distributed Tracing）的困難。",[363,608,609],{},"也就是說，microservices 解決了「系統規模問題」，但引入了「系統複雜度問題」。",[373,611],{},[358,613,615],{"id":614},"什麼時候適合使用-microservices","什麼時候適合使用 Microservices？",[363,617,618],{},"你可以用一個簡單的判斷原則：",[620,621,622],"blockquote",{},[363,623,624,627,630],{},[383,625,626],{},"如果你的系統還很小，請先使用 Monolith。",[628,629],"br",{},[383,631,632],{},"如果你的系統已經開始出現 scaling、部署、團隊協作問題，再考慮 microservices。",[363,634,635],{},"很多成功公司都是從 monolith 開始，逐步演進到 microservices，而不是一開始就採用。",[373,637],{},[358,639,640],{"id":640},"總結",[363,642,643],{},"Microservices 架構的核心價值，在於將一個大型系統拆分為多個可獨立運作的小服務。這種設計帶來了更好的擴展性、部署彈性、技術自由度與團隊協作效率。但同時，它也會引入分散式系統的複雜性。",[363,645,646],{},"因此，是否採用 microservices，應基於你的系統規模、團隊結構與實際需求來做出判斷。",{"title":422,"searchDepth":648,"depth":648,"links":649},2,[650,651,652,653,654,655,656,657,658,659,660,661],{"id":360,"depth":648,"text":361},{"id":377,"depth":648,"text":378},{"id":430,"depth":648,"text":431},{"id":439,"depth":648,"text":440},{"id":468,"depth":648,"text":469},{"id":505,"depth":648,"text":506},{"id":540,"depth":648,"text":541},{"id":563,"depth":648,"text":564},{"id":592,"depth":648,"text":593},{"id":601,"depth":648,"text":602},{"id":614,"depth":648,"text":615},{"id":640,"depth":648,"text":640},"深入了解 microservices 架構的核心概念，並探討其在現代系統設計中的優勢與實際應用場景。","md",null,{"category":203,"date":666,"tags":667},"2026-04-11",[668,669,670,671,672],"microservices","system_design","backend","architecture","scalability",true,{"title":271,"description":662},"TxtEFeS5kBWTmo_OnGbPOvN0wnBkS1atI2MNiVoLq98",[677,679],{"title":267,"path":268,"stem":269,"description":678,"children":-1},"用最直覺的方式理解 Zeabur 內網機制，學會在同一個 Project 中讓服務彼此連線，避免 localhost 與 IP 的常見錯誤。",{"title":275,"path":276,"stem":277,"description":680,"children":-1},"從零開始理解 Nginx 的核心功能，包含反向代理、負載平衡與靜態資源處理，並延伸比較 Kubernetes 在現代架構中的角色差異。",1776690846784]