Domain Driven Design Application Example, built with Lumen 5.3 and Doctrine.
Domain Driven Design approach help us write and maintain our core business preserved from technology dependencies. With the aid of ubiquitous language you could model your Domain and use thirdy part technologies to fit your needs. There are some DDD concepts, that application does not implement as: ValueObject, multiple Entites. The main purpose of this example is to give you a start point in terms of architecture, given the density of DDD, a simple example could not exhaust all the subject. The follow example implements a Store with products and product categories.
The Application Services are understood as Entrypoint for Domain. There is one Controller, Service Application and Service Provider by Domain. Providers map Contracts and Implementations.
mv Application/Lumen53/env_example Application/Lumen53/.env
php artisan migrate --path="../../database/migrations/"
e.g. GET localhost/Lumen-Doctrine-DDD-Example/Application/Lumen53/public/api/v1/products
http://www.zankavtaskin.com/2013/09/applied-domain-driven-design-ddd-part-1.html https://www.youtube.com/watch?v=pL9XeNjy_z4&list=PLx4mLirQvMeV0uNpo1UaculL-djjI8eTz https://www.youtube.com/watch?v=yPvef9R3k-M https://www.youtube.com/watch?v=dnUFEg68ESM
Davi dos Santos - [email protected]
Nicolas Escouto - [email protected]
Isolation of framework dependency in Application concerns
Use of YML for mappings
Use of JMS serialization with YML