architecture
WhatsApp System Design
It feels instant—but behind the scenes, there's a beautifully orchestrated system at work.
Here’s a breakdown of the WhatsApp Message Flow:
• Your message is encrypted instantly and sent to WhatsApp’s servers.
• The server checks if the recipient is online or offline.
• If online → message is delivered and synced across devices.
• If offline → message is queued and delivered once they’re back online.
• Read receipts are sent back when the user reads your message.
• And yes — all this happens within seconds, securely and efficiently.
Let's Explore the fascinating world of WhatsApp's architecture, breaking down the key components that make it all work seamlessly.
𝐋𝐨𝐜𝐚𝐥 𝐒𝐐𝐋𝐢𝐭𝐞 𝐃𝐁: Where your messages find a temporary home on your device.
𝐌𝐨𝐛𝐢𝐥𝐞 𝐔𝐬𝐞𝐫𝐬: Millions of users, each with their unique experience.
𝐂𝐮𝐬𝐭𝐨𝐦 𝐄𝐣𝐣𝐚𝐛𝐞𝐫𝐝 𝐒𝐞𝐫𝐯𝐞𝐫 𝐂𝐥𝐮𝐬𝐭𝐞𝐫: The powerhouse handling real-time communication.
𝐘𝐀𝐖𝐒 𝐒𝐞𝐫𝐯𝐞𝐫: Ensuring smooth interactions between users and servers.
𝐌𝐧𝐞𝐬𝐢𝐚 𝐃𝐁 𝐂𝐥𝐮𝐬𝐭𝐞𝐫, 𝐌𝐲𝐒𝐐𝐋, or 𝐏𝐨𝐬𝐭𝐠𝐫𝐞𝐬: Managing vast amounts of user data securely.
𝐑𝐢𝐚𝐤: The backbone for storage and quick retrieval of media and data.
𝐗𝐌𝐏𝐏 & 𝐇𝐓𝐓𝐏: Protocols enabling instant messaging and data transfer.
𝐆𝐂𝐌 / 𝐀𝐏𝐍𝐒: Pushing notifications to keep you updated, no matter the platform.
𝐖𝐫𝐢𝐭𝐞 𝐎𝐧𝐥𝐲, 𝐌𝐞𝐬𝐬𝐚𝐠𝐞 𝐀𝐫𝐜𝐡𝐢𝐯𝐞, 𝐎𝐟𝐟𝐥𝐢𝐧𝐞 𝐔𝐬𝐞𝐫𝐬: Features shaping your messaging experience.
𝐌𝐞𝐝𝐢𝐚, 𝐃𝐚𝐭𝐚, 𝐏𝐫𝐨𝐟𝐢𝐥𝐞, 𝐂𝐨𝐧𝐭𝐚𝐜𝐭𝐬: How your media and crucial information are managed.
𝐇𝐓𝐓𝐏: The bridge for web-based interactions with the WhatsApp platform.
#whatsapp #systemdesign #architecture #
𝐖𝐡𝐚𝐭 𝐫𝐞𝐚𝐥𝐥𝐲 𝐡𝐚𝐩𝐩𝐞𝐧𝐬 𝐰𝐡𝐞𝐧 𝐲𝐨𝐮 𝐡𝐢𝐭 𝐒𝐞𝐧𝐝 𝐨𝐧 𝐖𝐡𝐚𝐭𝐬𝐀𝐩𝐩?
• It feels instant—but behind the scenes, there's a beautifully orchestrated system at work.
• Here’s a breakdown of the WhatsApp Message Flow:
• Your message is encrypted instantly and sent to WhatsApp’s servers.
• The server checks if the recipient is online or offline.
• If online → message is delivered and synced across devices.
• If offline → message is queued and delivered once they’re back online.
• Read receipts are sent back when the user reads your message.
• And yes — all this happens within seconds, securely and efficiently.
• I visualized the entire architecture in this diagram to simplify how it works. Whether you're into system design, distributed systems, or just curious about real-time messaging, this is a great example to learn from.
• *There is a typo in step 4 it should be online
Software Architectural Patterns
These patterns are crucial in designing robust software systems.
→ Event Driven: This pattern allows different components to communicate through events.
→ Monolithic: All parts of the application are combined into a single unit, making it easier to manage but harder to scale.
→ Microservices: This approach breaks down the application into smaller, independent services, enhancing flexibility and scaling.
→ MVC (Model-View-Controller): This pattern separates data processing, user interface, and user input to make systems more manageable.
→ Master-Slave: This method distributes tasks among servers, improving performance and reliability.
#SoftwareArchitecturalPatterns #SoftwarePatterns #architecture
Architecture of a Web Application
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 user requests originate from the web browser. After DNS resolution, the requests reach the app servers. 3 – Load balancers and reverse proxies (such as Nginx & HAProxy) distribute user requests evenly across the web application servers.
4 – The requests can also be served by a Content Delivery Network (CDN).
5 – The web app communicates with backend services via APIs.
6 – The backend services interact with database servers or distributed caches to provide the data.
7 – Resource-intensive and long-running tasks are sent to job workers using a job queue.
8 – The full-text search service supports the search functionality. Tools like Elasticsearch and Apache Solr can help here.
9 – Monitoring tools (such as Sentry, Grafana, and Prometheus) store logs and help analyze data to ensure everything works fine.
10 – In case of issues, alerting services notify developers through platforms like Slack for quick resolution.
API Architectural Styles
REST: Sends HTTP requests from client to server and back. Widely used over HTTP.
GraphQL: Lets clients pull specific data in one query. Offers more control than REST.
WebSocket: Keeps a live connection for real-time, two-way communication.
gRPC: Uses Protocol Buffers for efficient messaging, often over HTTP/2.
MQTT: Lightweight protocol for IoT, sends messages via a broker.
Serverless: Executes APIs on demand, no server management needed. Perfect for cloud.
Six Software Architectural Patterns
API Architecture Styles
Microservice Architecture
Load Balancer:
This distributes incoming traffic across multiple backend services.
CDN (Content Delivery Network):
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.
API Gateway:
This handles incoming requests and routes them to the relevant services. It talks to the identity provider and service discovery.
Identity Provider:
This handles authentication and authorization for users.
Service Registry & Discovery:
Microservice registration and discovery happen in this component, and the API gateway looks for relevant services in this component to talk to.
Management:
This component is responsible for monitoring the services.
Microservices:
Microservices are designed and deployed in different domains. Each domain has its database.
Software Architectural PATTERNS
- Event-Driven Architecture: Components communicate through events, ideal for real-time processing.
- Layered Architecture: Organizes the system into layers, each with a specific responsibility, promoting separation of concerns.
- Monolithic Architecture: All functionalities are combined into a single application, suitable for simpler, smaller applications.
- Microservice Architecture: System is divided into independent services, each responsible for a specific function, allowing for scalability and flexibility.
- MVC (Model-View-Controller): Separates the application into three interconnected components to separate internal representations of information from the ways that information is presented and accepted.
- Master-Slave Architecture: One component (master) controls one or more other components (slaves), commonly used in database replication.
Benefits
- Reusability: Patterns can be reused across different projects, saving time and effort.
- Best Practices: Incorporate industry best practices, reducing common pitfalls.
- Communication: Provide a common language for developers, improving communication and understanding
