Module 6 of 10

Distributed Systems & Integration

Lessons

About This Module

As soon as a system is split across several services, machines, or data centres, new problems appear: networks fail, messages arrive late or twice, and different parts of the system can briefly disagree about the data. This module covers the ideas an architect needs to design and connect distributed systems that still behave reliably.

You'll start with the CAP theorem, the basic trade-off between consistency and availability, and see how eventual consistency works in practice. Then you'll look at how services talk to each other through message brokers such as Kafka and RabbitMQ, and how the saga pattern keeps data consistent across services without a single shared transaction.

Next up is Cloud & Infrastructure, where you'll look at the platforms and tooling that these distributed systems run on.

Lessons

4 videos
01

CAP Theorem Explained: Consistency vs Availability

A beginner-friendly guide to consistency, availability, and partition tolerance, and the trade-off every distributed system has to make.

02

Eventual Consistency: How It Works and Why It's Important

Eventual consistency as a consistency model for distributed systems where availability, scalability, and performance are key.

03

Kafka vs RabbitMQ

Why Kafka and RabbitMQ solve different problems, and how to pick between a message queue and an event streaming platform.

04

What Is the Saga Microservices Pattern?

The saga pattern for managing distributed transactions in microservices and keeping data eventually consistent across services.