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

The big rewrite


One temptation of developers is to rewrite an entire codebase. There are pros and cons for you to decide, and yes, it is often harder to read existing code than it is to write new code; but please do bear in mind that rewrites take time and can be hugely costly for your business.

Always bear in mind that the sum of your technical debt from any one project can never be greater than starting the project from scratch.

Maiz Lulkin wrote the following in a brilliant blog post:

"The problem of big rewrites is that they are a technical solution to a cultural problem."

Big rewrites are horribly inefficient, especially when you simply cannot guarantee that developers will know any better now. Architecting the new system and migrating the data inside the deadlines can be a tall order.

In addition to this, deploying the big rewrite can be hugely problematic; deploying such a change to the entire codebase of an application can be lethal. Try to deploy code regularly in frequent intervals...