Book Image

Domain-Driven Design in PHP

By : Keyvan Akbary, Carlos Buenosvinos, Christian Soronellas
Book Image

Domain-Driven Design in PHP

By: Keyvan Akbary, Carlos Buenosvinos, Christian Soronellas

Overview of this book

Domain-Driven Design (DDD) has arrived in the PHP community, but for all the talk, there is very little real code. Without being in a training session and with no PHP real examples, learning DDD can be challenging. This book changes all that. It details how to implement tactical DDD patterns and gives full examples of topics such as integrating Bounded Contexts with REST, and DDD messaging strategies. In this book, the authors show you, with tons of details and examples, how to properly design Entities, Value Objects, Services, Domain Events, Aggregates, Factories, Repositories, Services, and Application Services with PHP. They show how to apply Hexagonal Architecture within your application whether you use an open source framework or your own.

Related Content you might be interested in

Current Title:

Small book image
Domain-Driven Design in PHP
Keyvan Akbary | Carlos Buenosvinos | Christian Soronellas
Jun, 2017 | 394 pages
Small book image
Hands-On Domain-Driven Design with .NET Core
Alexey Zimarev
Apr, 2019 | 446 pages
Small book image
Domain-Driven Design with Golang
Matthew Boyle
Dec, 2022 | 204 pages
Small book image
Domain-Driven Design with Java - A Practitioner’s Guide
Premanand Chandrasekaran | Karthik Krishnan
Aug, 2022 | 302 pages
Table of Contents (24 chapters)
Title Page
Title Page
Credits
Credits
Foreword
Foreword
About the Authors
About the Authors
Acknowledgments
Acknowledgments
www.PacktPub.com
www.PacktPub.com
Customer Feedback
Customer Feedback
Dedication
Dedication
Preface
Preface
Free Chapter
1
Getting Started with Domain-Driven Design
Getting Started with Domain-Driven Design
Why Domain-Driven Design Matters
The Three Pillars of Domain-Driven Design
Considering Domain-Driven Design
The Tricky Parts
Strategical Overview
Related Movements: Microservices and Self-Contained Systems
Wrap-Up
2
Architectural Styles
Architectural Styles
The Good Old Days
Layered Architecture
Event Sourcing
Wrap-Up
3
Value Objects
Value Objects
Definition
Value Object vs. Entity
Currency and Money Example
Characteristics
Basic Types
Testing Value Objects
Persisting Value Objects
Security
Wrap-Up
4
Entities
Entities
Introduction
Objects Vs. Primitive Types
Identity Operation
Persisting Entities
Testing Entities
Validation
Entities and Domain Events
Wrap-Up
5
Services
Services
Application Services
Domain Services
Domain Services and Infrastructure Services
Testing Domain Services
Anemic Domain Models Vs Rich Domain Models
Wrap-Up
6
Domain-Events
Domain-Events
Introduction
Definition
Characteristics
Modeling Events
Doctrine Events
Persisting Domain Events
Publishing Events from the Domain Model
Spreading the news to Remote Bounded Contexts
Wrap-Up
7
Modules
Modules
General Overview
Leverage Modules in PHP
Bounded Contexts and Applications
Structuring Code in Modules
Wrap-Up
8
Aggregates
Aggregates
Introduction
Key Concepts
What Is an Aggregate?
Why Aggregates?
A Bit of History
Anatomy of an Aggregate
Aggregate Design Rules
Sample Application Service: User and Wishes
Transactions
Wrap Up
9
Factories
Factories
Factory Method on Aggregate Root
Factory on Service
Testing Factories
Wrap-Up
10
Repositories
Repositories
Definition
Repositories Are Not DAOs
Collection-Oriented Repositories
Persistence-Oriented Repository
Querying Repositories
Managing Transactions
Testing Repositories
Testing Your Services with In-Memory Implementations
Wrap-Up
11
Application
Application
Requests
Anatomy of an Application Service
Testing Application Services
Transactions
Security
Domain Events
Command Handlers
Wrap-Up
12
Integrating Bounded Contexts
Integrating Bounded Contexts
Integration Through the Data Store
Integration Relationships
Implementing Bounded Context Integrations
Wrap-Up
13
Hexagonal Architecture with PHP
Hexagonal Architecture with PHP
Introduction
First Approach
Repositories and the Persistence Edge
Decoupling Business and Persistence
Migrating our Persistence to Redis
Decouple Business and Web Framework
Rating an Idea Using the API
Console App Rating
Testing Rating an Idea UseCase
Testing Infrastructure
Arggg, So Many Dependencies!
Domain Services and Notification Hexagon Edge
Let's Recap
Hexagonal Architecture
Key Points
What's Next?
14
Bibliography
Bibliography
15
The End
The End

Bounded Contexts and Applications

If we take the example of a fictional company called BuyIt, which deals with an e-commerce Domain, it may make sense to create a different application for each of the different Bounded Contexts solving specific Domain areas.

If some of the different Bounded Contexts are Order Management, Payment Management, Catalog Management, and Inventory Management, we recommend having an application for each one: 

                    

Each application exposes any set of delivery mechanisms needed. With the microservices trend, more and more people build Bounded Contexts that end up exposing REST APIs to the outside world. However, a Bounded Context is more than just an API. Remember that an API is just one of many delivery mechanisms; a Bounded Context can provide a web interface to interact with too.

Note

Can Two Bounded Contexts Be in the Same Application? What about the Other Way Around? The best option is one Subdomain, one Bounded Context, and one application. If we...

Previous Section
End of Section 4
Next Section