There are two different approaches for invoking Application Services: a dedicated class per use case with a single execution method, and multiple Application Services and use cases inside the same class.
- Foreword
- Acknowledgments
- Dedication
- Preface
- Who Should Read This Book
- DDD and PHP Community
- Summary of Chapters
- Chapter 1: Getting Started with Domain-Driven Design
- Chapter 2: Architectural Styles
- Chapter 3: Value Objects
- Chapter 4: Entities
- Chapter 5: Domain Services
- Chapter 6: Domain-Events
- Chapter 7: Modules
- Chapter 8: Aggregates
- Chapter 9: Factories
- Chapter 10: Repositories
- Chapter 11: Application
- Chapter 12: Integrating Bounded Contexts
- Appendix: Hexagonal Architecture with PHP
- Code and Examples
- Getting Started with Domain-Driven Design
- Architectural Styles
- Value Objects
- Definition
- Value Object vs. Entity
- Currency and Money Example
- Characteristics
- Basic Types
- Testing Value Objects
- Persisting Value Objects
- Persisting Single Value Objects
- Serialized LOB and Ad Hoc ORM
- Serialized LOB with Doctrine
- NoSQL
- Security
- Wrap-Up
- Entities
- Services
- Domain-Events
- Modules
- Aggregates
- Factories
- Repositories
- Application
- Integrating Bounded Contexts
- 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?
- Bibliography
- The End
Execution
-
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.