Domain Events¶
📕 Articles¶
- How to publish and handle Domain Events
- Handling Domain Events: Missing Part
- The Outbox Pattern
- Domain Events – Salvation
- Domain events: design and implementation
- Events on the outside, on the inside and at the core
- Strengthening your domain: Domain Events
- Don’t publish Domain Events, return them!
- Using Domain Events within a .NET Core Microservice
- Domain Events Pattern Example
- A better domain events pattern
- Strengthening your domain: a primer
- Strengthening your domain: Domain Events
- Implementing event-based communication between microservices (integration events)
- DDD and Messaging Architectures
- Domain events: simple and reliable solution
- Domain Events Pattern Example
- Domain Events
- Patterns for Decoupling in Distributed Systems: Explicit Public Events
- Immediate Domain Event Salvation with MediatR
- Design a No Duplicates Rule in your Domain Model?
- From Domain to Integration Events
- Domain Events - Before Persistence
- Domain Events - After Persistence
- Decoupling Logic with Domain Events - Domain-Driven Design w/ TypeScript
- Domain Events in DDD
- Practical DDD in Golang: Domain Event
- Simple Domain Events with EFCore and MediatR
- Design validations in the domain model layer
- 6 Code Smells with your CQRS Events – and How to Avoid Them
- Domain Events - Alexey Zimarev
- .NET Domain Events Using MediatR
- Leaking Value Objects from your Domain ⭐
- Why we Avoid Putting Value Objects in Events ⭐
- Domain-Driven Design: Domain Events and Integration Events in .Net ⭐
- From domain events to infrastructure - thinking out loud about possible approaches I don’t hate
- Internal and external events, or how to design event-driven API
🚀 Samples¶
- ardalis/CleanArchitecture
- vietnam-devs/coolstore-microservices
- thangchung/clean-architecture-dotnet
- vkhorikov/DddAndEFCore
- kgrzybek/modular-monolith-with-ddd/blob/90ab9b20a1c6e11700e8b357929c5f792b2b32bf/src/BuildingBlocks/Infrastructure/UnitOfWork.cs#L27
- ardalis/AggregateEvents