Open-source alternatives to Dotnet Cqrs Intro

This project is a reference implementation of domain-driven design patterns and a sample of command query responsibility segregation. It provides a collection of event-driven microservices that demonstrate the practical application of architectural principles for structuring complex software systems. The implementation separates read and write models through an event journal and organizes services into bounded contexts to maintain clear functional boundaries. It coordinates business logic by dispatching and consuming domain events to synchronize different modules. The project covers a range

This project provides a structured boilerplate for building Node.js REST APIs, implementing clean architecture principles to isolate business logic from external frameworks and data sources. It serves as a template for organizing complex backend services by enforcing a strict separation of concerns between domain entities, infrastructure, and interface layers. The architecture distinguishes itself through a modular, plugin-based server design built on the Hapi.js framework. It utilizes a dependency injection container to decouple business logic from concrete implementations, ensuring that ser

Complete working example of using Domain Driven Design (DDD), Hexagonal Architecture, CQRS, Event Sourcing (ES), Event Driven Architecture (EDA), Behaviour Driven Development (BDD) using TypeScript and NestJS. Like what you see? Don't forget to star! ⭐ ^^^

Examples of implementation CQRS with Event Sourcing - evolutionary approach

This is a .NET skeleton project to introduce the concepts of Domain Driven Design and loosely coupled layers. You can use this solution as a starting point to build loosely coupled and composable applications where the Domain is at the heart of the project.

DDD CQRS ADR PHP Symfony example

Domain Driven Design (DDD) N-LayeredArchitecture with .Net Core 2

This project is a reference implementation and architectural sample of Domain-Driven Design. It serves as a codebase demonstrating how to align software design with a specific business domain to manage complex business logic. The implementation functions as a reporting system that receives and processes data via JSON payloads. It utilizes a structured domain model to define and automate business workflows and handle state changes. The architecture partitions the system into distinct application and domain layers, utilizing aggregate roots for consistency and the repository pattern for data a

PHP 7 Version of the cargo sample used in Eric Evans DDD book

Domain Driven Design, CQRS, & Event Sourcing Example using GetEventStore, CommonDomain, NServiceBus, Entity Framework, SQL Server, SignalR

This project is a reference implementation of Domain-Driven Design patterns, functional domain modeling, and event-driven state coordination. It demonstrates the application of strategic and tactical design patterns to manage complex business requirements. The implementation utilizes a functional domain model with pure functions and immutable objects to manage state transitions and side effects. It features a Command Query Responsibility Segregation architecture to separate read and write models, alongside event-driven coordination to maintain consistency across autonomous business boundaries

This repository contains code that accompanies presentation ASC LAB team gave at meetup about “Creating better code with Domain Driven Design”.

GSD (Get your Stuff Done) | Basic Todo list for demonstrating CQRS/Command Sourcing in Haskell

Event-Sourcing and Domain-Driven Design with F# and EventStore

DDD-CqRS sample v2.0 project that helps you with starting out advanced domain modeling using Spring, JPA and testing

A sample DDD/CQRS project using KOTLIN :beer:

Just a simple implementation of DDD clean architecture pattern. It also contains the exaplanation about the concepts that supports this implementation.

EquinoxProject is an ASP.NET 9 web application template and reference implementation for building enterprise software. It provides a structural boilerplate centered on clean architecture, domain-driven design, and the separation of read and write operations through a command query responsibility segregation framework. The project incorporates event sourcing to track the history of business entities as a sequence of events for auditing and state reconstruction. It utilizes a layered approach to decouple business logic from external dependencies and frameworks. The system includes capabilities

Wishlist, a sample application on Symfony 3 and Vue.js built with DDD in mind

The Gopher API, is a simple CRUD API for formative purpose, we're building it while writing the posts of the blog.

Simple CQRS example

Task management system based on .NET 8 with Microservices, DDD, CQRS, Event Sourcing and Testing Concepts

EventStorming workshop, this is a hands-on workshop. Contains such topics: DDD, Event storming, Specification by example. Including the AWS product : Serverless Lambda , DynamoDB, Fargate, CloudWatch.

Sample implementation and comparison of various approaches to building DDD applications. Useful as a baseline to quickly start a DDD dot net project.

This project is a template for a DDD-based Modulith. It uses Symfony and is fully Docker-compatible and can be executed directly with docker compose up. The modules are integrated via IntegrationEvents, which can be found in the extra Integration directory.

API to convert Bikram Sambat (BS) (also called Vikram Samvat) dates to Gregorian dates and vice-versa

eShopOnWeb is a reference application for ASP.NET Core that demonstrates a sample e-commerce site. It serves as a template for building scalable services using domain-driven design to separate business logic from infrastructure and data access. The project implements a decoupled messaging pattern through a request pipeline to separate web controllers from application logic. It utilizes a repository pattern to abstract data persistence and isolate the core application logic from the specific database storage mechanism. The application covers a broad surface of web capabilities, including user