Arpit's Newsletter read by 80000+ engineers
Weekly essays on real-world system design, distributed systems, or a deep dive into some super-clever algorithm.
Say, we are building a Social Network and anytime someone reacts to your post, you need to be notified. So, how should the Reaction service talk to the Notification service to send out a notification?
The communication would be much simpler and reliable, just a function call if it was a monolith; but things become tricky as we go distributed.
Microservices need to talk to each other to exchange information and get things done; and there are two categories of communication patterns - Synchronous and Asynchronous.
Communication is synchronous when one service sends a request to another service and waits for the response before proceeding further.
The most common implementation of Sync communication is over HTTP using protocols like REST, GraphQL, and gRPC.
The communication is asynchronous when the one service sends a request to another service and does NOT wait for the response; instead, it continues with its own execution.
Async communication is most commonly implemented using a message broker like RabbitMQ, SQS, Kafka, Kinesis, etc.
Here's the video ⤵
Alongside my daily work, I also teach some highly practical courses, with a no-fluff no-nonsense approach, that are designed to spark engineering curiosity and help you ace your career.
A no-fluff masterclass that helps experienced engineers form the right intuition to design and implement highly scalable, fault-tolerant, extensible, and available systems.
An in-depth and self-paced course for absolute beginners to become great at designing and implementing scalable, available, and extensible systems.
A self-paced and hands-on course covering Redis internals - data structures, algorithms, and some core features by re-implementing them in Go.
Arpit's Newsletter read by 80000+ engineers
Weekly essays on real-world system design, distributed systems, or a deep dive into some super-clever algorithm.