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

Why anti-patterns matter


Most programmers come from a background of adopting some form of anti-pattern until eventually realizing how it doesn't scale or doesn't work well. When I was 17 and in my first job as an apprentice developer, I would be whisked down to London Monday-to-Friday, somehow compressing my suit and my totally black clothing into a surprisingly miniscule suitcase, and would learn about software development. On Fridays, we were often released for a half-day at 12:00 but I would pre-book my company train tickets in the afternoon so I would spend my time in fast-food restaurants or coffee shops working on simple projects. Every week, when I came back and tried to scale one of these solutions I would realize new scalability issues and code quality issues. Of course, I had done development before, but these were largely dealing with either brand new incredibly short programming tasks, using pre-made frameworks or dealing with legacy code where the architecture had already been...