open atlas · learning, in the open topic 11
Queues, Streams, Eventing Kafka partitions, exactly-once, outbox, CDC.
✦ 8 units ◆ 45 lessons
Start here At-most-once, at-least-once, exactly-once: the three delivery contracts
1 unit 01 Delivery guarantees: at-most-once, at-least-once, and the truth about exactly-once Exactly-once delivery is impossible (Two Generals). At-least-once + idempotent consumer = effectively-once. Kafka transactions, SQS visibility timeout, and the outbox pattern are the production tools.
2 unit 02 Kafka partitions How Kafka distributes messages across partitions, assigns consumer group members, and why partition count is a one-way door.
3 unit 03 RabbitMQ exchanges and routing Direct, fanout, topic, and headers exchanges — how binding keys route messages and where each pattern fits in production.
4 unit 04 Message ordering guarantees Why total order is expensive, how Kafka delivers per-partition FIFO, and the practical patterns for preserving order in distributed consumers.
5 unit 05 The transactional outbox pattern Write a database row and a message atomically — how the outbox table, polling relay, and CDC eliminate the dual-write problem.
6 unit 06 Change-Data Capture Reading the database write-ahead log to stream every row change as an event — Debezium, Postgres logical replication, and the operational gotchas.
7 unit 07 Designing UX for eventual consistency Optimistic UI, conflict resolution, progress indicators, and retry affordances — making asynchronous systems feel responsive to users.
8 unit 08 Putting it together: event-driven service mesh End-to-end design of an order-processing pipeline — outbox, Kafka topics, consumer groups, CDC, dead-letter queues, and observability.
The summit · orbit reached You can see the whole topic now. Every unit, from the underground to the orbit. Queues, Streams, Eventing is one constellation in the atlas — climb another topic and watch the next one light up.