Event-driven architecture

Systems whose parts talk by announcing events instead of calling each other: how the messages travel, what goes wrong with them, the patterns built on top, and how it looks in .NET.

Trails

EDA

Event-driven foundations

still growing

Explain what event-driven architecture is, and choose between queues, topics and streams for a message.

0/8 read

Builds on: Async in C#

8 notes
  1. Why event-driven
  2. Events, commands and queries
  3. Anatomy of an event
  4. Queue vs topic
  5. Broker vs event stream
  6. Partitions, offsets and consumer groups
  7. One tool, both shapes
  8. Routing and topology

Trails

EDAREL

Reliable messaging

still growing

Build publishers and consumers that stay correct when messages are duplicated, late, out of order or failing.

0/9 read

Builds on: Event-driven foundations

9 notes
  1. Eventual consistency
  2. Delivery guarantees
  3. Idempotent consumers
  4. Message ordering
  5. Retries and backoff
  6. Dead-letter queues
  7. Dead letters and ordered messages
  8. Outbox and inbox
  9. Event versioning

Trails

EDAPAT

Event-driven patterns

still growing

Choose between thin and fat events, coordinate a workflow across services with a saga, and decide when CQRS, event sourcing or event-driven design is worth its cost.

0/7 read

Builds on: Reliable messaging

7 notes
  1. Event notification vs state transfer
  2. Asking another service for data
  3. Choreography vs orchestration
  4. Sagas
  5. CQRS
  6. Event sourcing
  7. When to use event-driven design

Trails

EDANET

Event-driven in .NET

still growing

Build event-driven features in .NET, from an in-process queue to a broker with a framework or Dapr, and trace an event across services.

0/7 read

Builds on: Event-driven patterns, ASP.NET Core fundamentals

7 notes
  1. In-process events
  2. Mediator pattern in .NET
  3. Brokers and clients for .NET
  4. Messaging frameworks for .NET
  5. MassTransit, from contract to outbox
  6. Dapr pub/sub
  7. Observing event flows

All topics →