Book Image

Mastering PHP Design Patterns

By : Junade Ali
Book Image

Mastering PHP Design Patterns

By: Junade Ali

Overview of this book

Design patterns are a clever way to solve common architectural issues that arise during software development. With an increase in demand for enhanced programming techniques and the versatile nature of PHP, a deep understanding of PHP design patterns is critical to achieve efficiency while coding. This comprehensive guide will show you how to achieve better organization structure over your code through learning common methodologies to solve architectural problems. You’ll also learn about the new functionalities that PHP 7 has to offer. Starting with a brief introduction to design patterns, you quickly dive deep into the three main architectural patterns: Creational, Behavioral, and Structural popularly known as the Gang of Four patterns. Over the course of the book, you will get a deep understanding of object creation mechanisms, advanced techniques that address issues concerned with linking objects together, and improved methods to access your code. You will also learn about Anti-Patterns and the best methodologies to adopt when building a PHP 7 application. With a concluding chapter on best practices, this book is a complete guide that will equip you to utilize design patterns in PHP 7 to achieve maximum productivity, ensuring an enhanced software development experience.
Table of Contents (14 chapters)
Mastering PHP Design Patterns
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface

Decorator


A Decorator is simply what adds additional functionality to an individual class without affecting the behavior of other objects from the same class.

The Single Responsibility Principle, simply put by Robert C. Martin (who I introduced at the start of this chapter), is that a class should have only one reason to change.

The principle states that every module or class should have a single responsibility and that responsibility should be entirely encapsulated by that class. All services of the class should align with that responsibility. Martin summarized this by defining the responsibility as follows:

"a charge assigned to a unique actor to signify its accountabilities concerning a unique business task".

By using the Decorator design pattern, we are able to ensure that functionality is divided between classes with unique areas of concern, thus adhering to the Single Responsibility Principle.

Let's start off by declaring our Book interface. This is what we expect our Books to be able...