You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
-10Lines changed: 0 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,16 +22,6 @@ java implementation. The same applies for our version.
22
22
The application layer is based on ZF2 and we use Doctrine2 to persist our aggregates.
23
23
This would be a common combination in a large PHP project but both frameworks are not required. They just make our life easier and let us focus on the Domain-Driven Design implementation. Both can be replaced with any other PHP based components.
24
24
25
-
<b>If you like our shipping system, become a stargazer or watch the project and come back soon. We have some interssting topics in the pipeline. Here is a preview of what follows next:</b>
26
-
27
-
+ Introduce an application layer to better shield the domain
28
-
+ Switch to hexagonal architecture
29
-
+ A deep dive into Entities, ValueObjects, Aggregates and DomainServices
30
-
+ Communication across bounded contexts
31
-
+ CQRS and asynchonous Messaging
32
-
+ Use EventSourcing to persist Aggregates
33
-
34
-
35
25
Iterative Implementation
36
26
------------------------
37
27
To go with you when you read the book, our sample has a [release of each chapter](https://github.com/codeliner/php-ddd-cargo-sample#chapter-overview). So you can
0 commit comments