Giter VIP home page Giter VIP logo

ddd-cqrs-example's Introduction

About

This is an example of implementation and my vision of practical CQRS, DDD, ADR, hexagonal architecture and directory structure. Project has entities Task and User. All UI is the REST endpoints.

What is done

  • Hexagonal Architecture (Ports directory for external endpoints)
  • CQRS (based on symfony messenger component command/query buses with middlewares)
  • DDD: directory structure (used sensiolabs-de/deptrac to control layers dependencies)
  • DDD: core bounded context
  • DDD: domain events implementation
  • DDD: example of specification in User entity that requires a db query

To do

  • Add another bounded context
  • Add anti-corruption layer for interaction between contexts

My assumptions

  • I placed entities public getters and private setters into the traits with *GS suffix to make entities a little bit clear (phpstorm tracks fine all references to entity classes) anyway you can put getters with setters in the same class
  • Unfortunately mysql has a poor performance with primary uuids. Of course prefer application generated uuid if database supports them.

How to install the project

  • bash setup_env.sh dev - to setup .env.local docker/.env
  • make dc_up - docker-compose up
  • make setup_dev - composer install, migrations and so on
  • make run php bin/console app:create-user - create a user
  • http://127.0.0.1:888/api/doc https://127.0.0.1:444/api/doc - api doc

Some words about docker

In project is used workplace container for code manipulations, CI or building. It was created for preventing of pollution of working containers (php-fpm) of unused in request, building tools like nodejs, composer, dev libs and so on. Also was created a local user based on host machine user PUID PGID to resolve conflicts with file permissions.

make dev - jump into workplace container

CI

make dev
//in container execute
make analyze

Implementation

Used symfony messenger component to create transactional command bus, query bus and event bus. Query model represented by DTOs. Domain and Command layers are covered by unit tests.

├── Core (Core bounded context)
│   ├── Application
│   │   ├── Command
│   │   │   ├── AuthToken
│   │   │   ├── Task
│   │   │   └── User
│   │   ├── Query
│   │       └── Task
│   ├── Domain
│   │   └── Model
│   │       ├── Task
│   │       └── User
│   ├── Infrastructure
│   │   └── Repository
│   └── Ports
│       ├── Cli
│       └── Rest
└── Shared
    ├── Domain
    └── Infrastructure

ddd-cqrs-example's People

Contributors

ferrius avatar

Watchers

 avatar  avatar

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.