About the Book
Finding the best way to organize your code is one of the hardest parts of coding.
Determing the best way to architect your application is a very important step in development. Heading in the wrong direction can lead to a nightmare later, and make it nearly impossible to refactor the application to meet new demands, and can make properly testing the application a pain. While the methods outlined in this book aren't the only way to go about developing an application, they do provide a framework for developing applications that are:
- Testable
- Refactorable
- Easy to work with
- Easy to maintain
In this book, we cover the Clean Architecture, coined by Uncle Bob, and how to implement it in PHP.
-
Feedback
Share this book
Table of Contents
-
-
Introduction
- Organization
- The Author
- A Word about Coding Style
- Cover Credits
-
Introduction
-
The Problem With Code
-
Writing Good Code is Hard
- Writing Bad Code is Easy
- We Can’t Test Anything
- Change Breaks Everything
- We Live or Die by the Framework
- We Want to Use All the Libraries
- Writing Good Code
-
What is Architecture?
- What does Architecture Look Like?
- Layers of Software
- Examples of Poor Architecture
- Costs of Poor Architecture
-
Coupling, The Enemy
- Spaghetti Coupling
- OOP Coupling
- Why is Coupling the Enemy?
- How do we Reduce Coupling?
-
Writing Good Code is Hard
-
Your Decoupling Toolbox
-
Design Patterns, A Primer
- The Factory Patterns
- Repository Pattern
- Adapter Pattern
- Strategy Pattern
- Learning More Design Patterns
-
SOLID Design Principles
- Single Responsibility Principle
- Open/Closed Principle
- Liskov Substitution Principle
- Interface Segregation Principle
- Dependency Inversion Principle
- Applying SOLID Principles
-
Dependency Injection
- Inversion of Control
- When to use Dependency Injection
- Handling Many Dependencies
- Are we still coupling?
-
Defining a Contract with Interfaces
- Interfaces in PHP
- Using Interfaces as Type Hints
- Using Interfaces as a Contract
- Making Third Party Code Conform to Contracts
-
Abstracting with Adapters
- Setting up the Adapter
- How does this help?
-
Design Patterns, A Primer
-
The Clean Architecture
-
MVC, and it’s Limitations
- MVC in a Diagram
- The MVC Components
- Routing
- MVC Isn’t Good Enough
- Obese Models
- More Layers for All of the Things!
-
The Clean Architecture
- The Clean Architecture
- The Onion Architecture
-
Framework Independence
- The Problem with Frameworks
- Framework Independence
- This is a Lot of Work
-
Database Independence
- Domain Models
- Domain Services
- Database Infrastructure / Persistence
- Organizing the Code
- Wrapping it Up
-
External Agency Independence
- Using Interfaces, Adapters and Dependency Injection
- Benefits
-
MVC, and it’s Limitations
-
A Case Study in Clean Architecture
-
The Billing System
- Application Workflow
- Prerequisites
-
Building Our Domain
- Setting up the Project
- Creating the Entities
- Domain Services
- Wrapping it Up
-
The Billing System
About the Author
Kristopher has been developing business grade PHP applications for over 9 years. He is active in the PHP community as a founder of the Grand Rapids PHP Developers group (GrPhpDev), and is committed to fostering and increasing knowledge and skillset of the local community.
He lives in Grand Rapids, Michigan with his wife, Ashley, and their collection of four cats.