<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>architecture —   christova  </title>
    <link>https://christova.writeas.com/tag:architecture</link>
    <description>&lt;b&gt;&lt;h3&gt;Tech Articles&lt;/h3&gt;&lt;/b&gt;&lt;br/&gt;&lt;b&gt;Collated from various sources. Full copyright remains with original authors.&lt;/b&gt;</description>
    <pubDate>Mon, 16 Nov 2026 16:29:11 +0000</pubDate>
    <item>
      <title>Spotify System Design</title>
      <link>https://christova.writeas.com/spotify-system-design?pk_campaign=rss-feed</link>
      <description>#Spotify #SystemDesign #Architecture</description>
      <content:encoded><![CDATA[<p><img src="https://i.snap.as/JM2ScBG3.jpg" alt=""/></p>

<p><a href="https://christova.writeas.com/tag:Spotify" class="hashtag" rel="nofollow ugc"><span>#</span><span class="p-category">Spotify</span></a> <a href="https://christova.writeas.com/tag:SystemDesign" class="hashtag" rel="nofollow ugc"><span>#</span><span class="p-category">SystemDesign</span></a> <a href="https://christova.writeas.com/tag:Architecture" class="hashtag" rel="nofollow ugc"><span>#</span><span class="p-category">Architecture</span></a></p>
]]></content:encoded>
      <guid>https://christova.writeas.com/spotify-system-design</guid>
      <pubDate>Thu, 08 Oct 2026 18:39:39 +0000</pubDate>
    </item>
    <item>
      <title>Microservice Architecture</title>
      <link>https://christova.writeas.com/microservice-architecture-nyfn?pk_campaign=rss-feed</link>
      <description>#microservices #architecture</description>
      <content:encoded><![CDATA[<p><img src="https://i.snap.as/v7P8oMbR.jpg" alt=""/></p>

<p><a href="https://christova.writeas.com/tag:microservices" class="hashtag" rel="nofollow ugc"><span>#</span><span class="p-category">microservices</span></a> <a href="https://christova.writeas.com/tag:architecture" class="hashtag" rel="nofollow ugc"><span>#</span><span class="p-category">architecture</span></a></p>
]]></content:encoded>
      <guid>https://christova.writeas.com/microservice-architecture-nyfn</guid>
      <pubDate>Thu, 26 Mar 2026 07:29:16 +0000</pubDate>
    </item>
    <item>
      <title>WhatsApp System Design</title>
      <link>https://christova.writeas.com/whatsapp-system-design?pk_campaign=rss-feed</link>
      <description>It feels instant—but behind the scenes, there&#39;s a beautifully orchestrated system at work. Here’s a breakdown of the WhatsApp Message Flo...</description>
      <content:encoded><![CDATA[<p>It feels instant—but behind the scenes, there&#39;s a beautifully orchestrated system at work.</p>

<p>Here’s a breakdown of the WhatsApp Message Flow:</p>

<p>• Your message is encrypted instantly and sent to WhatsApp’s servers.</p>

<p>• The server checks if the recipient is online or offline.</p>

<p>• If online → message is delivered and synced across devices.</p>

<p>• If offline → message is queued and delivered once they’re back online.</p>

<p>• Read receipts are sent back when the user reads your message.</p>

<p>• And yes — all this happens within seconds, securely and efficiently.</p>

<p><img src="https://i.snap.as/Jsudh8aE.gif" alt=""/></p>

<p>Let&#39;s Explore the fascinating world of WhatsApp&#39;s architecture, breaking down the key components that make it all work seamlessly.</p>

<p>𝐋𝐨𝐜𝐚𝐥 𝐒𝐐𝐋𝐢𝐭𝐞 𝐃𝐁: Where your messages find a temporary home on your device.</p>

<p>𝐌𝐨𝐛𝐢𝐥𝐞 𝐔𝐬𝐞𝐫𝐬: Millions of users, each with their unique experience.</p>

<p>𝐂𝐮𝐬𝐭𝐨𝐦 𝐄𝐣𝐣𝐚𝐛𝐞𝐫𝐝 𝐒𝐞𝐫𝐯𝐞𝐫 𝐂𝐥𝐮𝐬𝐭𝐞𝐫: The powerhouse handling real-time communication.</p>

<p>𝐘𝐀𝐖𝐒 𝐒𝐞𝐫𝐯𝐞𝐫: Ensuring smooth interactions between users and servers.</p>

<p>𝐌𝐧𝐞𝐬𝐢𝐚 𝐃𝐁 𝐂𝐥𝐮𝐬𝐭𝐞𝐫, 𝐌𝐲𝐒𝐐𝐋, or 𝐏𝐨𝐬𝐭𝐠𝐫𝐞𝐬: Managing vast amounts of user data securely.</p>

<p>𝐑𝐢𝐚𝐤: The backbone for storage and quick retrieval of media and data.</p>

<p>𝐗𝐌𝐏𝐏 &amp; 𝐇𝐓𝐓𝐏: Protocols enabling instant messaging and data transfer.</p>

<p>𝐆𝐂𝐌 / 𝐀𝐏𝐍𝐒: Pushing notifications to keep you updated, no matter the platform.</p>

<p>𝐖𝐫𝐢𝐭𝐞 𝐎𝐧𝐥𝐲, 𝐌𝐞𝐬𝐬𝐚𝐠𝐞 𝐀𝐫𝐜𝐡𝐢𝐯𝐞, 𝐎𝐟𝐟𝐥𝐢𝐧𝐞 𝐔𝐬𝐞𝐫𝐬: Features shaping your messaging experience.</p>

<p>𝐌𝐞𝐝𝐢𝐚, 𝐃𝐚𝐭𝐚, 𝐏𝐫𝐨𝐟𝐢𝐥𝐞, 𝐂𝐨𝐧𝐭𝐚𝐜𝐭𝐬: How your media and crucial information are managed.</p>

<p>𝐇𝐓𝐓𝐏: The bridge for web-based interactions with the WhatsApp platform.</p>

<p><a href="https://christova.writeas.com/tag:whatsapp" class="hashtag" rel="nofollow ugc"><span>#</span><span class="p-category">whatsapp</span></a> <a href="https://christova.writeas.com/tag:systemdesign" class="hashtag" rel="nofollow ugc"><span>#</span><span class="p-category">systemdesign</span></a> <a href="https://christova.writeas.com/tag:architecture" class="hashtag" rel="nofollow ugc"><span>#</span><span class="p-category">architecture</span></a> #</p>

<p><img src="https://i.snap.as/QGiS0XUP.gif" alt=""/></p>

<p><a href="https://christova.writeas.com/tag:whatsapp" class="hashtag" rel="nofollow ugc"><span>#</span><span class="p-category">whatsapp</span></a> &#39;<a href="https://christova.writeas.com/tag:howwhatsappworks" class="hashtag" rel="nofollow ugc"><span>#</span><span class="p-category">howwhatsappworks</span></a></p>

<p>𝐖𝐡𝐚𝐭 𝐫𝐞𝐚𝐥𝐥𝐲 𝐡𝐚𝐩𝐩𝐞𝐧𝐬 𝐰𝐡𝐞𝐧 𝐲𝐨𝐮 𝐡𝐢𝐭 𝐒𝐞𝐧𝐝 𝐨𝐧 𝐖𝐡𝐚𝐭𝐬𝐀𝐩𝐩?</p>

<p><strong>•</strong> It feels instant—but behind the scenes, there&#39;s a beautifully orchestrated system at work.</p>

<p><strong>•</strong> Here’s a breakdown of the WhatsApp Message Flow:</p>

<p><strong>•</strong> Your message is encrypted instantly and sent to WhatsApp’s servers.</p>

<p><strong>•</strong> The server checks if the recipient is online or offline.</p>

<p><strong>•</strong> If online → message is delivered and synced across devices.</p>

<p><strong>•</strong> If offline → message is queued and delivered once they’re back online.</p>

<p><strong>•</strong> Read receipts are sent back when the user reads your message.</p>

<p><strong>•</strong> And yes — all this happens within seconds, securely and efficiently.</p>

<p><strong>•</strong> I visualized the entire architecture in this diagram to simplify how it works.
Whether you&#39;re into system design, distributed systems, or just curious about real-time messaging, this is a great example to learn from.</p>

<p><strong>•</strong> *There is a typo in step 4 it should be online</p>
]]></content:encoded>
      <guid>https://christova.writeas.com/whatsapp-system-design</guid>
      <pubDate>Wed, 25 Mar 2026 20:20:32 +0000</pubDate>
    </item>
    <item>
      <title>Software Architectural Patterns</title>
      <link>https://christova.writeas.com/software-architectural-patterns-qcww?pk_campaign=rss-feed</link>
      <description>These patterns are crucial in designing robust software systems. → Event Driven: This pattern allows different components to communicate ...</description>
      <content:encoded><![CDATA[<p><img src="https://media.licdn.com/dms/image/v2/D4D22AQGp62H3EKexhQ/feedshare-shrink_2048_1536/B4DZUPShCzGkAo-/0/1739718296588?e=2147483647&amp;v=beta&amp;t=w0p9m6fOd3p3ySCdja0oAirMVawDZyGek-Hsn-tuAkc" alt="Every Developer should know these Software Architectural Patterns | Ashish  Misal"/></p>

<p>These patterns are crucial in designing robust software systems.</p>

<p>→ Event Driven: This pattern allows different components to communicate through events.</p>

<p>→ Monolithic: All parts of the application are combined into a single unit, making it easier to manage but harder to scale.</p>

<p>→ Microservices: This approach breaks down the application into smaller, independent services, enhancing flexibility and scaling.</p>

<p>→ MVC (Model-View-Controller): This pattern separates data processing, user interface, and user input to make systems more manageable.</p>

<p>→ Master-Slave: This method distributes tasks among servers, improving performance and reliability.</p>

<p><a href="https://christova.writeas.com/tag:SoftwareArchitecturalPatterns" class="hashtag" rel="nofollow ugc"><span>#</span><span class="p-category">SoftwareArchitecturalPatterns</span></a> <a href="https://christova.writeas.com/tag:SoftwarePatterns" class="hashtag" rel="nofollow ugc"><span>#</span><span class="p-category">SoftwarePatterns</span></a> <a href="https://christova.writeas.com/tag:architecture" class="hashtag" rel="nofollow ugc"><span>#</span><span class="p-category">architecture</span></a></p>
]]></content:encoded>
      <guid>https://christova.writeas.com/software-architectural-patterns-qcww</guid>
      <pubDate>Sun, 12 Jan 2025 15:18:46 +0000</pubDate>
    </item>
    <item>
      <title>Architecture of a Web Application</title>
      <link>https://christova.writeas.com/architecture-of-a-web-application?pk_campaign=rss-feed</link>
      <description>1 – It all starts with CI/CD pipelines that deploy code to the server instances. Tools like Jenkins and GitHub help over here. 2 – The us...</description>
      <content:encoded><![CDATA[<p><img src="https://i.snap.as/wTi1WU2o.jpg" alt=""/></p>

<p><strong>1</strong> – It all starts with CI/CD pipelines that deploy code to the server instances. Tools like Jenkins and GitHub help over here.</p>

<p><strong>2</strong> – The user requests originate from the web browser. After DNS resolution, the requests reach the app servers. <strong>3</strong> – Load balancers and reverse proxies (such as Nginx &amp; HAProxy) distribute user requests evenly across the web application servers.</p>

<p><strong>4</strong> – The requests can also be served by a Content Delivery Network (CDN).</p>

<p><strong>5</strong> – The web app communicates with backend services via APIs.</p>

<p><strong>6</strong> – The backend services interact with database servers or distributed caches to provide the data.</p>

<p><strong>7</strong> – Resource-intensive and long-running tasks are sent to job workers using a job queue.</p>

<p><strong>8</strong> – The full-text search service supports the search functionality. Tools like Elasticsearch and Apache Solr can help here.</p>

<p><strong>9</strong> – Monitoring tools (such as Sentry, Grafana, and Prometheus) store logs and help analyze data to ensure everything works fine.</p>

<p><strong>10</strong> – In case of issues, alerting services notify developers through platforms like Slack for quick resolution.</p>

<p><a href="https://christova.writeas.com/tag:WebApp" class="hashtag" rel="nofollow ugc"><span>#</span><span class="p-category">WebApp</span></a> <a href="https://christova.writeas.com/tag:architecture" class="hashtag" rel="nofollow ugc"><span>#</span><span class="p-category">architecture</span></a> <a href="https://christova.writeas.com/tag:WebApplication" class="hashtag" rel="nofollow ugc"><span>#</span><span class="p-category">WebApplication</span></a></p>
]]></content:encoded>
      <guid>https://christova.writeas.com/architecture-of-a-web-application</guid>
      <pubDate>Sat, 09 Nov 2024 03:28:57 +0000</pubDate>
    </item>
    <item>
      <title>API Architectural Styles</title>
      <link>https://christova.writeas.com/api-architectural-styles?pk_campaign=rss-feed</link>
      <description>REST: Sends HTTP requests from client to server and back. Widely used over HTTP. GraphQL: Lets clients pull specific data in one query. O...</description>
      <content:encoded><![CDATA[<p><img src="https://i.snap.as/O05Ru5Bo.gif" alt=""/></p>

<p><strong>REST</strong>: Sends HTTP requests from client to server and back. Widely used over HTTP.</p>

<p><strong>GraphQL</strong>: Lets clients pull specific data in one query. Offers more control than REST.</p>

<p><strong>WebSocket</strong>: Keeps a live connection for real-time, two-way communication.</p>

<p><strong>gRPC</strong>: Uses Protocol Buffers for efficient messaging, often over HTTP/2.</p>

<p><strong>MQTT</strong>: Lightweight protocol for IoT, sends messages via a broker.</p>

<p><strong>Serverless</strong>: Executes APIs on demand, no server management needed. Perfect for cloud.</p>

<p><a href="https://christova.writeas.com/tag:APIs" class="hashtag" rel="nofollow ugc"><span>#</span><span class="p-category">APIs</span></a> <a href="https://christova.writeas.com/tag:architecture" class="hashtag" rel="nofollow ugc"><span>#</span><span class="p-category">architecture</span></a></p>
]]></content:encoded>
      <guid>https://christova.writeas.com/api-architectural-styles</guid>
      <pubDate>Fri, 01 Nov 2024 23:47:11 +0000</pubDate>
    </item>
    <item>
      <title>Six Software Architectural Patterns</title>
      <link>https://christova.writeas.com/six-software-architectural-patterns?pk_campaign=rss-feed</link>
      <description>#architecture #patterns #ArchtecturalPatterns</description>
      <content:encoded><![CDATA[<p><img src="https://i.snap.as/mHA9KWF9.png" alt=""/></p>

<p><a href="https://christova.writeas.com/tag:architecture" class="hashtag" rel="nofollow ugc"><span>#</span><span class="p-category">architecture</span></a> <a href="https://christova.writeas.com/tag:patterns" class="hashtag" rel="nofollow ugc"><span>#</span><span class="p-category">patterns</span></a> <a href="https://christova.writeas.com/tag:ArchtecturalPatterns" class="hashtag" rel="nofollow ugc"><span>#</span><span class="p-category">ArchtecturalPatterns</span></a></p>
]]></content:encoded>
      <guid>https://christova.writeas.com/six-software-architectural-patterns</guid>
      <pubDate>Wed, 30 Oct 2024 19:59:30 +0000</pubDate>
    </item>
    <item>
      <title>API Architecture Styles</title>
      <link>https://christova.writeas.com/api-architecture-styles?pk_campaign=rss-feed</link>
      <description>#API #APIs #Architecture #REST #SOAP #GraphQL #WebSocket #Webhook</description>
      <content:encoded><![CDATA[<p><img src="https://i.snap.as/P6pbcPu8.jpg" alt=""/></p>

<p><a href="https://christova.writeas.com/tag:API" class="hashtag" rel="nofollow ugc"><span>#</span><span class="p-category">API</span></a> <a href="https://christova.writeas.com/tag:APIs" class="hashtag" rel="nofollow ugc"><span>#</span><span class="p-category">APIs</span></a> <a href="https://christova.writeas.com/tag:Architecture" class="hashtag" rel="nofollow ugc"><span>#</span><span class="p-category">Architecture</span></a> <a href="https://christova.writeas.com/tag:REST" class="hashtag" rel="nofollow ugc"><span>#</span><span class="p-category">REST</span></a> <a href="https://christova.writeas.com/tag:SOAP" class="hashtag" rel="nofollow ugc"><span>#</span><span class="p-category">SOAP</span></a> <a href="https://christova.writeas.com/tag:GraphQL" class="hashtag" rel="nofollow ugc"><span>#</span><span class="p-category">GraphQL</span></a> <a href="https://christova.writeas.com/tag:WebSocket" class="hashtag" rel="nofollow ugc"><span>#</span><span class="p-category">WebSocket</span></a> <a href="https://christova.writeas.com/tag:Webhook" class="hashtag" rel="nofollow ugc"><span>#</span><span class="p-category">Webhook</span></a></p>
]]></content:encoded>
      <guid>https://christova.writeas.com/api-architecture-styles</guid>
      <pubDate>Fri, 11 Oct 2024 22:10:58 +0000</pubDate>
    </item>
    <item>
      <title>Microservice Architecture</title>
      <link>https://christova.writeas.com/microservice-architecture?pk_campaign=rss-feed</link>
      <description>Load Balancer: This distributes incoming traffic across multiple backend services. CDN (Content Delivery Network): CDN is a group of geog...</description>
      <content:encoded><![CDATA[<p><img src="https://i.snap.as/pwi1rUx8.jpg" alt=""/></p>

<p><strong>Load Balancer:</strong></p>

<p>This distributes incoming traffic across multiple backend services.</p>

<p><strong>CDN (Content Delivery Network):</strong></p>

<p>CDN is a group of geographically distributed servers that hold static content for faster delivery. The clients look for content in CDN first, then progress to backend services.</p>

<p><strong>API Gateway:</strong></p>

<p>This handles incoming requests and routes them to the relevant services. It talks to the identity provider and service discovery.</p>

<p><strong>Identity Provider:</strong></p>

<p>This handles authentication and authorization for users.</p>

<p><strong>Service Registry &amp; Discovery:</strong></p>

<p>Microservice registration and discovery happen in this component, and the API gateway looks for relevant services in this component to talk to.</p>

<p><strong>Management:</strong></p>

<p>This component is responsible for monitoring the services.</p>

<p><strong>Microservices:</strong></p>

<p>Microservices are designed and deployed in different domains. Each domain has its database.</p>

<p><a href="https://christova.writeas.com/tag:microservice" class="hashtag" rel="nofollow ugc"><span>#</span><span class="p-category">microservice</span></a> <a href="https://christova.writeas.com/tag:architecture" class="hashtag" rel="nofollow ugc"><span>#</span><span class="p-category">architecture</span></a></p>
]]></content:encoded>
      <guid>https://christova.writeas.com/microservice-architecture</guid>
      <pubDate>Wed, 02 Oct 2024 07:11:17 +0000</pubDate>
    </item>
    <item>
      <title>Software Architectural PATTERNS</title>
      <link>https://christova.writeas.com/software-architectural-patterns-f5bc?pk_campaign=rss-feed</link>
      <description>Event-Driven Architecture: Components communicate through events, ideal for real-time processing. Layered Architecture: Organizes the sys...</description>
      <content:encoded><![CDATA[<p><img src="https://substackcdn.com/image/fetch/w_1456,c_limit,f_auto,q_auto:good,fl_lossy/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F37da2535-a515-41b6-9b63-6a9bc9357cbf_800x991.gif" alt=""/></p>
<ul><li><strong>Event-Driven Architecture:</strong> Components communicate through events, ideal for real-time processing.</li>
<li><strong>Layered Architecture:</strong> Organizes the system into layers, each with a specific responsibility, promoting separation of concerns.</li>
<li><strong>Monolithic Architecture:</strong> All functionalities are combined into a single application, suitable for simpler, smaller applications.</li>
<li><strong>Microservice Architecture:</strong> System is divided into independent services, each responsible for a specific function, allowing for scalability and flexibility.</li>
<li><strong>MVC (Model-View-Controller):</strong> Separates the application into three interconnected components to separate internal representations of information from the ways that information is presented and accepted.</li>
<li><strong>Master-Slave Architecture:</strong> One component (master) controls one or more other components (slaves), commonly used in database replication.</li></ul>

<h1 id="benefits"><strong>Benefits</strong></h1>
<ul><li><strong>Reusability:</strong> Patterns can be reused across different projects, saving time and effort.</li>
<li><strong>Best Practices:</strong> Incorporate industry best practices, reducing common pitfalls.</li>
<li><strong>Communication:</strong> Provide a common language for developers, improving communication and understanding</li></ul>

<p><a href="https://christova.writeas.com/tag:architecture" class="hashtag" rel="nofollow ugc"><span>#</span><span class="p-category">architecture</span></a> <a href="https://christova.writeas.com/tag:DesignPatterns" class="hashtag" rel="nofollow ugc"><span>#</span><span class="p-category">DesignPatterns</span></a></p>
]]></content:encoded>
      <guid>https://christova.writeas.com/software-architectural-patterns-f5bc</guid>
      <pubDate>Fri, 09 Aug 2024 20:13:58 +0000</pubDate>
    </item>
  </channel>
</rss>