Domain-Driven Design in PHP

Foreword by Matthias Noback

Preface

1. Who Should Read This Book
2. DDD and PHP Community
3. Summary of Chapters
4. Code and Examples
5. Acknowledgements

About the Authors

1. Carlos Buenosvinos
2. Christian Soronellas
3. Keyvan Akbary

Getting Started with Domain-Driven Design

1. Why Domain-Driven Design Matters
2. The Three Pillars of Domain-Driven Design
3. Considering Domain-Driven Design
4. The Tricky Parts
5. Strategical Overview
6. Related Movements: Microservices and Self-Contained Systems
7. Exercise
8. Wrap-Up

Architectural Styles

1. Spaghetti Architecture
2. Layered Architecture
3. DTOs Instead of Model Instances?
4. Hexagonal Architecture: Inverting Dependencies
5. The Dependency Inversion Principle
6. Command Query Responsibility Segregation (CQRS)
7. Command Query Separation (CQS)
8. Event Sourcing
9. Wrap-Up

Value Objects

1. Definition
2. Exercise
3. Value Object vs. Entity
4. Exercise
5. Currency and Money Example
6. Extra Validations for Currency
7. Characteristics
8. static vs. self
9. Exercise
10. Basic Types
11. Testing Value Objects
12. Persisting Value Objects
13. Why Doctrine?
14. Constructors
15. Surrogate Attributes
16. Why Use XML Mapping?
17. Time to Discuss
18. Exercise
19. Exercise
20. Exercise
21. Security
22. Wrap-Up

Entities

1. Introduction
2. Objects vs. Primitive Types
3. Identity Operation
4. Exercise
5. Persisting Entities
6. What’s an Annotation?
7. Testing Entities
8. Validation
9. Entities and Domain Events
10. Wrap-Up

Services

1. Application Services
2. Domain Services
3. Domain Services and Infrastructure Services
4. Testing Domain Services
5. Anemic Domain Models vs. Rich Domain Models
6. Wrap-Up

Domain Events

1. Introduction
2. Definition
3. Exercise
4. Characteristics
5. Symfony Event Dispatcher
6. Modeling Events
7. Why Not the Whole User Entity?
8. Doctrine Events
9. Persisting Domain Events
10. Publishing Events from the Domain Model
11. Other Strategy for Publishing Domain Events
12. Exercise
13. Spreading the News to Remote Bounded Contexts
14. Why an Exchange Name?
15. Exercise
16. Wrap-Up

Modules

1. General Overview
2. Leverage Modules in PHP
3. What about PHAR files?
4. Bounded Contexts and Applications
5. Can Two Bounded Contexts Be in the Same Application? What about the Other Way Around?
6. Structuring Code in Modules
7. Should We Place Repositories, Factories, Domain Events, and Services in Their Own Subfolders?
8. Wrap-Up

Aggregates

1. Introduction
2. Key Concepts
3. What Is an Aggregate?
4. Why Aggregates?
5. A Bit of History
6. Anatomy of an Aggregate
7. Aggregate Design Rules
8. Sample Application Service: User and Wishes
9. Render the Number of Wishes
10. Transactions
11. Wrap Up

Factories

1. Factory Method on Aggregate Root
2. Factory on Service
3. Testing Factories
4. Wrap-Up

Repositories

1. Definition
2. Repositories Are Not DAOs
3. Collection-Oriented Repositories
4. Exercise
5. Persistence-Oriented Repository
6. Extra Behavior
7. Querying Repositories
8. Managing Transactions
9. Testing Repositories
10. Testing Your Services with In-Memory Implementations
11. Wrap-Up

Application

1. Requests
2. Anatomy of an Application Service
3. Handling Exceptions
4. Is It Bad to Use a Dependency Injection Container?
5. Testing Application Services
6. Transactions
7. Security
8. Domain Events
9. Command Handlers
10. Wrap-Up

Integrating Bounded Contexts

1. Integration Through the Data Store
2. Integration Relationships
3. Implementing Bounded Context Integrations
4. Wrap-Up

Appendix: Hexagonal Architecture with PHP

1. Introduction
2. First Approach
3. Repositories and the Persistence Edge
4. Decoupling Business and Persistence
5. Migrating our Persistence to Redis
6. Decouple Business and Web Framework
7. Rating an idea using the API
8. Console app rating
9. Testing Rating an Idea UseCase
10. Testing Infrastructure
11. Arggg, So Many Dependencies!
12. Domain Services and Notification Hexagon Edge
13. Let’s Recap
14. Hexagonal Architecture
15. Key Points
16. What’s Next?

The End

Bibliography