Repository Index

Web Application ASP.NET 9 using Clean Architecture, DDD, CQRS, Event Sourcing and a lot of good practices

• equinox
• cqrs
• architecture
• asp-net-core

KurrentDB is a database that's engineered for modern software applications and event-driven architectures. Its event-native design simplifies data modeling and preserves data integrity while the integrated streaming engine solves distributed messaging challenges and ensures data consistency.

• cqrs
• eventsourcing
• eventstore
• event-sourcing

Async/await first CQRS+ES and DDD framework for .NET

• eventsourcing
• cqrs
• dotnet
• async-await

A persistence agnostic Event Store for .NET

.NET event sourced domain driven design model via NServiceBus and GetEventStore

• eventstore
• nservicebus
• ddd
• eventsourcing

A state-of-the-art distributed system using Reactive DDD as uncertainty modeling, Event Storming as subdomain decomposition, Event Sourcing as an eventual persistence mechanism, CQRS, Async Projections, Microservices for individual deployable units, Event-driven Architecture for efficient integration, and Clean Architecture as domain-centric design

• cqrs
• ddd
• clean-architecture
• event-sourcing

Fork of dotnet-architecture/eShopOnContainers in full DDD/CQRS design using my own patterns

• ddd
• domain-driven-design
• nservicebus
• eventstore

Implementation of basic Todo app via tastejs/todomvc in C#/Typescript with eventsourcing, cqrs, and domain driven design

• ddd
• domain-driven-design
• nservicebus
• eventstore

DDD+CQRS+Event-sourcing examples using EventFlow following CQRS-ES architecture. It is configured with RabbitMQ, MongoDB(Snapshot store), PostgreSQL(Read store), EventStore(GES). It's targeted to .Net Core 2.2 and include docker compose file.

• eventflow
• cqrs
• cqrs-es-architecture
• ges

A library to facilitate communication between CommandService and QueryService. The Idea is when any event occures in commandService, it should be persisted in QueryService in MongoDb, SqlServer, MySql and PostgreSQL