Displaying 1 to 20 from 36 results

eventhorizon - CQRS/ES toolkit for Go

  •    Go

Event Horizon is a CQRS/ES toolkit for Go. CQRS stands for Command Query Responsibility Segregation and is a technique where object access (the Query part) and modification (the Command part) are separated from each other. This helps in designing complex data models where the actions can be totally independent from the data output.

ddd-dynamic - Domain Driven Design in Python, Ruby and other dynamic languages resources


This is an attempt to collect all info about Domain Driven Design the World knows in dynamic languages (Python, Ruby, PHP etc). Not only DDD but all worthy info about layered and clean architecture with separation of business logic from infrastructure and framework code. Hexagonal design in Django - Python, Django, contains some code.


  •    DotNet

A .NET based DDD application development framework.


  •    CSharp

A .NET implementation of Domain Driven Design (DDD) sample application based on Eric Evans' examples included in his great book. Project is intended to be used in training, demonstration and experiments.

N-Tier Entity Framework


The N-Tier Entity Framework extends Microsoft's Entity Framework (EF) to provide support for n-tier software solutions while keeping its simplicity.

NHibernate with ASP.net Problem-Design-Solution

  •    ASPNET

Project to accompany the NHibernate with ASP.net Problem-Design-Solution Wrox Blox by Scott Millett, demonstrating how to use NHibernate within a web context (ASP.net) whilst applying enterprise design patterns and following a Domain Driven Design methodology.

.NET Domain-Driven Design with C#: Problem-Design-Solution

  •    DotNet

The purpose of this project is to hold the source code for my latest book, .NET Domain-Driven Design with C#: Problem-Design-Solution. The book is one large case study of a real-world application, named SmartCA, which is a smart client application implemented with the latest ...

Tiny Library CQRS


Tiny Library CQRS is a small demonstration project which demonstrates the concept of Domain Driven Design and the CQRS architecture pattern. This project relies on the Apworks DDD framework.

SellAndBuy (Domain Driven Design sample using .Net 4.0)

  •    DotNet

Domain Driven Design (DDD) Behavior Driven Design (BDD) Test Driven Design (TDD) .Net 4.0 NHibernate SpecFlow NUnit NSubstitute MVC 3 Razor Engine WCF NLayer

Ultralight O/R mapper


O/R mapping in C# in 400 lines of code. No binary distribution, this framework is meant to be embedded in your (small scale) projects. Please feel free to use and update this code for any purpose.

Preservation Noticing Accelerator


This code is the engine for a litigation management solution configured for managing the preservation notice component within an E-Discovery project. Currently, the data store that the engine is using is a SharePoint 2007 instance (it could be either WSS or MOSS). The code h...

node-eventstore - EventStore Implementation in node.js

  •    Javascript

Node-eventstore is a node.js module for multiple databases. It can be very useful as eventstore if you work with (d)ddd, cqrs, eventsourcing, commands and events, etc.

node-cqrs-domain - Node-cqrs-domain is a node

  •    Javascript

Node-cqrs-domain is a node.js module based on node-eventstore. It can be very useful as domain component if you work with (d)ddd, cqrs, eventdenormalizer, host, etc. You can use this for example in you custom command handlers.

node-cqrs-eventdenormalizer - Node-cqrs-eventdenormalizer is a node

  •    Javascript

Node-cqrs-eventdenormalizer is a node.js module that implements the cqrs pattern. It can be very useful as eventdenormalizer component if you work with (d)ddd, cqrs, domain, host, etc. The values describes the path to that property in the event message.

node-cqrs-saga - Node-cqrs-saga is a node

  •    Javascript

Node-cqrs-saga is a node.js module that helps to implement the sagas in cqrs. It can be very useful as domain component if you work with (d)ddd, cqrs, eventdenormalizer, host, etc. The values describes the path to that property in the event message.

ddd-house - 🏠 Building a house with DDD


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.