<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
    <channel>
        <title>Distributed Systems - Tag - ThanhLD Site</title>
        <link>https://ducthanh98.github.io/tags/distributed-systems/</link>
        <description>Distributed Systems - Tag - ThanhLD Site</description>
        <generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Sun, 12 Nov 2023 22:53:37 &#43;0700</lastBuildDate><atom:link href="https://ducthanh98.github.io/tags/distributed-systems/" rel="self" type="application/rss+xml" /><item>
    <title>Microservices Architecture &amp; Distributed System Design Patterns</title>
    <link>https://ducthanh98.github.io/posts/microservice/</link>
    <pubDate>Sun, 12 Nov 2023 22:53:37 &#43;0700</pubDate>
    <author>ThanhLD</author>
    <guid>https://ducthanh98.github.io/posts/microservice/</guid>
    <description><![CDATA[Core architectural principles, decomposition strategies, distributed design patterns, resilience mechanisms, and deployment strategies for microservices systems.
Monolith vs Microservices Architecture Criteria Monolithic Architecture Microservices Architecture Development Single codebase, straightforward local debugging Multiple repositories/services, polyglot tech stacks Deployment Single unit deployment (all-or-nothing) Independent, continuous deployments per service Scaling Vertical scaling or duplicate entire monolith Horizontal, granular scaling based on resource needs Fault Isolation Low (a memory leak or crash impacts whole app) High (failure in one service does not crash others) Complexity Low operational overhead; high codebase coupling High operational complexity (distributed network overhead) Microservice Decomposition Strategies How to break down a domain into microservices:]]></description>
</item>
</channel>
</rss>
