All Projects → jenkoian → ddd-house

jenkoian / ddd-house

Licence: other
🏠 Building a house with DDD

Projects that are alternatives of or similar to ddd-house

Architecture
.NET 6, ASP.NET Core 6, Entity Framework Core 6, C# 10, Angular 13, Clean Code, SOLID, DDD.
Stars: ✭ 2,285 (+5913.16%)
Mutual labels:  ddd, domain-driven-design
EcommerceDDD
Experimental full-stack application using Domain-Driven Design, CQRS, and Event Sourcing.
Stars: ✭ 178 (+368.42%)
Mutual labels:  ddd, domain-driven-design
Kreta
Modern project management solution
Stars: ✭ 177 (+365.79%)
Mutual labels:  ddd, domain-driven-design
Event Sourcing Jambo
An Hexagonal Architecture with DDD + Aggregates + Event Sourcing using .NET Core, Kafka e MongoDB (Blog Engine)
Stars: ✭ 159 (+318.42%)
Mutual labels:  ddd, domain-driven-design
ddderr
👺 Reflection-free Domain-Driven errors for Go.
Stars: ✭ 29 (-23.68%)
Mutual labels:  ddd, domain-driven-design
Stove
Domain Driven Design oriented application framework, meets CRUD needs
Stars: ✭ 160 (+321.05%)
Mutual labels:  ddd, domain-driven-design
Library
This is a project of a library, driven by real business requirements. We use techniques strongly connected with Domain Driven Design, Behavior-Driven Development, Event Storming, User Story Mapping.
Stars: ✭ 2,685 (+6965.79%)
Mutual labels:  ddd, domain-driven-design
Nlayerappv3
Domain Driven Design (DDD) N-LayeredArchitecture with .Net Core 2
Stars: ✭ 138 (+263.16%)
Mutual labels:  ddd, domain-driven-design
tactical-ddd
lightweight helpers that I find myself implementing over and over again related to DDD/Event Sourcing tactical patterns, such as Value Objects, Entities, AggregateRoots, EntityIds etc...
Stars: ✭ 33 (-13.16%)
Mutual labels:  ddd, domain-driven-design
Dotnet New Caju
Learn Clean Architecture with .NET Core 3.0 🔥
Stars: ✭ 228 (+500%)
Mutual labels:  ddd, domain-driven-design
Laravel Api Templates
Laravel API starter kit collection using different structures.
Stars: ✭ 149 (+292.11%)
Mutual labels:  ddd, domain-driven-design
repository
[PHP 7] Implementation and definition of a base Repository in Domain land.
Stars: ✭ 26 (-31.58%)
Mutual labels:  ddd, domain-driven-design
Eventflow
Async/await first CQRS+ES and DDD framework for .NET
Stars: ✭ 1,932 (+4984.21%)
Mutual labels:  ddd, domain-driven-design
Revo
Event Sourcing, CQRS and DDD framework for C#/.NET Core.
Stars: ✭ 162 (+326.32%)
Mutual labels:  ddd, domain-driven-design
Goes
Go Event Sourcing made easy
Stars: ✭ 144 (+278.95%)
Mutual labels:  ddd, domain-driven-design
Messagebus
A MessageBus (CommandBus, EventBus and QueryBus) implementation in PHP7
Stars: ✭ 178 (+368.42%)
Mutual labels:  ddd, domain-driven-design
Eventflow.example
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.
Stars: ✭ 131 (+244.74%)
Mutual labels:  ddd, domain-driven-design
Todomvc Ddd Cqrs Eventsourcing
Implementation of basic Todo app via tastejs/todomvc in C#/Typescript with eventsourcing, cqrs, and domain driven design
Stars: ✭ 134 (+252.63%)
Mutual labels:  ddd, domain-driven-design
Run Aspnetcore
A starter kit for your next ASP.NET Core web application. Boilerplate for ASP.NET Core reference application, demonstrating a layered application architecture with applying Clean Architecture and DDD best practices. Download 100+ page eBook PDF from here ->
Stars: ✭ 227 (+497.37%)
Mutual labels:  ddd, domain-driven-design
clean-architecture
Package for isolate your domain code from framework dependency using DDD concepts.
Stars: ✭ 93 (+144.74%)
Mutual labels:  ddd, domain-driven-design

DDD House

This repository is used to 'build a house with DDD'. It's a means of getting my head around a few concepts I've been learning recently. Such as the following:

The biggest thing I aim to achieve is the separation of layers. Using modelling by example to work from the middle out. Cleanly separating the domain from the rest of the application.

I aim to do this iteratively with each stage of my work in a separate branch. For example, version1 branch may be just setting up some basic behat features through to a fully featured domain layer, with infrastructure supporting a front end that communicates to the domain.

How to use this repo

View each branch along with the notes in the commit message to see what each commit adds.

Demo app

The demo app is viewable at https://dddhouse.herokuapp.com/

CLI app

A gif of the CLI version in action:

Inspiration

As mentioned the blog post by Everzet on 'Modelling by example' was a big inspiration behind this kind of approach. Definitely read it. Funnily enough, he has been working on a similar repository which I wasn't aware of until recently called 'pick-my-talks'. It doesn't cover things like commands and handler but is probably a better example of modelling by exmaple than this, so definitely recommend checking that out also.

Other sources of inspiration include:

TODO

  • Add acceptance tests as a next step.
  • Look into possibility of adding some kind of persistence of house state.
Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].