How to run eShopOnContainersDDD on Windows?

It's currently Linux-only due to Docker image dependencies; you might use WSL or a VM, but setup isn't officially supported and can be tricky.

What's the difference between eShopOnContainers and this DDD version?

The DDD version fully implements event sourcing and CQRS with Aggregates.NET, while the original uses traditional persistence, making it better for learning event-driven architectures but more complex.

How to add a new read model in this architecture?

Create a service that subscribes to the event log and builds a projection using MongoDB or Elasticsearch, similar to existing models shown in the codebase.

Is eShopOnContainersDDD production ready?

No, it's an illustrative example with known bugs and experimental code, intended for learning rather than direct production use.

What are the performance costs of event sourcing here?

Event sourcing adds overhead in event storage and replay, but it enhances auditability and scalability for complex domains, as detailed in the architecture overview.

How to troubleshoot docker-compose setup issues?

Check the Linux-cli scripts, ensure licenses are exported, and verify IP addresses; the wiki may offer tips, but community support is limited.

eShopOnContainersDDD

MITC#

A fully event-sourced e-commerce microservices example built with DDD, CQRS, and Aggregates.NET patterns.

GitHub

320 stars45 forks0 contributors

What is eShopOnContainersDDD?

eShopOnContainersDDD is a fork of Microsoft's eShopOnContainers project, reimplemented as a fully event-sourced e-commerce application using Domain-Driven Design (DDD) and Command Query Responsibility Segregation (CQRS) patterns. It demonstrates how to build a distributed microservices system where all state changes are captured as events, providing a complete audit log and enabling flexible read models for different business needs.

Target Audience

Developers and architects interested in learning or implementing DDD, CQRS, and event sourcing in .NET microservices applications, particularly those building scalable e-commerce or distributed systems.

Value Proposition

It offers a practical, open-source example of a production-like event-sourced architecture using Aggregates.NET, making complex distributed systems more understandable and maintainable by separating concerns and providing a single source of truth through event logs.

Overview

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

Use Cases

Best For

Learning event sourcing and CQRS patterns in a real-world .NET application

Related Projects

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub

Building scalable e-commerce platforms with microservices

Implementing Domain-Driven Design in distributed systems

Creating audit-friendly applications with complete change histories

Developing systems where multiple departments need different views of the same data

Practicing containerized deployment with Docker and microservices

Not Ideal For

Teams needing rapid prototyping without complex distributed system setup
Developers on Windows environments due to Linux-only Docker requirements
Projects avoiding proprietary library licenses like ServiceStack
Applications where simple CRUD operations suffice, making event sourcing overkill

Pros & Cons

Pros

Comprehensive Event Sourcing Example

Demonstrates a fully event-sourced application using Aggregates.NET, providing a practical implementation of DDD and CQRS with clear architecture diagrams.

Clear Separation of Concerns

Strictly implements CQRS to separate commands and queries, improving scalability and maintainability as explained in the logical overview.

Flexible Read Models

Uses event logs to generate tailored read models for different business needs, such as for warehouse and marketing departments, illustrated in the event sourcing diagram.

Containerized Microservices

Employs Docker for containerization, showcasing modern deployment practices in a distributed microservices architecture.