BEGINNER · 8 MODULES · 64 LESSONS
Event-Driven Architecture
Turn a fragile chain of direct calls into an event-driven system, where one service going down doesn't stop the rest and duplicates do no harm.
- For you if
- You have a backend process where one failed call takes down the whole flow.
- By the end
- You'll know how to consume events idempotently, publish them with an outbox, and when event sourcing, CQRS, and sagas pay off.
- You need
- Basic Python and a working grasp of databases and transactions. No messaging experience needed.

Curriculum
01De la llamada al evento
05Event sourcing
06CQRS (separar la escritura de la lectura)
- Module introduction: separating what writes from what reads
- Command and query: two operations, two models
- The projection and the read model
- Eventual consistency: the read model lags behind
- One log, many read models
- Read only from the read model (and rebuild it)
- When to use CQRS (and when it's overkill)
- Project: split Mercado's order flow into writing and reading
07Sagas — transacciones distribuidas
08Proyecto — vuelve dirigido por eventos el flujo de pedidos de Mercado
- Module introduction: the return journey, with the complete system running
- Modeling the order events
- Publishing the order events with the outbox
- Idempotent, decoupled consumers
- The checkout saga with compensation
- Measuring synchronous versus event-driven
- The architecture decision record
- Project: make Mercado's order flow event-driven
Reviews
What students say
These reviews are from enrolled students who completed at least 50% of the course. We moderate reviews only on content grounds (spam, offensive language, personal data), never for being critical or negative.
No approved reviews yet.
Be the first to share your experience!