Decouple services and process event streams.
Message queues (RabbitMQ, SQS) and log streams (Kafka) decouple producers and consumers, smooth bursts and enable asynchronous processing. Guarantees: at-most/at-least/exactly once; ordering per partition. Event streaming supports analytics and event sourcing.
An order service publishes events consumed by inventory and email services.
Message queues decouple services so that one can send work without waiting for the other, which improves resilience and throughput.
Decouple services and process event streams.
Message queues decouple services so that one can send work without waiting for the other, which improves resilience and throughput.
A queue usually removes a message once it is consumed, while a stream keeps a durable log that many consumers can read at their own pace.
A failure in one service does not immediately block the sender, and each side can scale and change on its own schedule.
Typical applications include sending order events to a queue so that the shipping service processes them later, buffering sensor readings during a burst so the database is not overwhelmed and processing a stream of events for analytics in real time.
Study "Caching and load balancing" first (topic 83 of 104 in Software & Computing). It covers the groundwork this topic builds on.
Pub/sub. Consumer groups. Backpressure.
An order service publishes events consumed by inventory and email services.
The next topic is "Cryptography basics", which builds directly on this one.
It is classed as Advanced in Software & Computing (topic 84 of 104). It is an advanced topic. It assumes you are comfortable with the intermediate topics in Software & Computing.
Want to practise? Open the interactive course for quick checks, quizzes, simulations and progress tracking.