Wolverine Idioms for MediatR Users
Compares Wolverine and MediatR frameworks, showing how Wolverine's idioms can simplify code for developers familiar with MediatR patterns.
Compares Wolverine and MediatR frameworks, showing how Wolverine's idioms can simplify code for developers familiar with MediatR patterns.
A guide to implementing the MediatR library in a .NET API, covering its benefits for decoupling, testability, and cleaner code.
Explains the CQRS pattern, its benefits for scaling read/write operations independently, and when to use it in software architecture.
A guide to implementing Clean Architecture folder structure in .NET solutions, covering Domain, Application, Infrastructure, and Presentation layers.
A developer shares 100 personal opinions on programming, software development practices, tools, and team methodologies.
Explains the Mediator pattern and CQRS, demonstrating their implementation and benefits in a C# application using MediatR.
A developer shares key talks that guided their journey into event sourcing and event-driven development, covering foundational concepts and practical applications.
A guide to implementing a simple CQRS pattern using raw SQL and Domain-Driven Design (DDD) principles in a .NET Core REST API application.
Announcing the Kindle release of 'Microsoft .NET: Architecting Applications for the Enterprise' (NAA4E), covering DDD, CQRS, and enterprise architecture.
Explains how to implement auto-retry for concurrent commands in CQRS using the ncqrs framework to handle ConcurrencyExceptions.
A developer explores how to improve traditional CRUD applications by integrating concepts from CQRS and event-driven architecture.
A developer's curated list of resources, links, and videos for learning the CQRS (Command Query Responsibility Segregation) architectural pattern and Event Sourcing.
A developer shares key lessons learned from applying Domain-Driven Design (DDD) and Command Query Responsibility Segregation (CQRS) in an agile project.
Notes from a DDD/CQRS course covering aggregates, commands, queries, and handling consistency without distributed transactions.