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

Agile software architecture


Many organizations are leaning towards adopting an Agile form of project management. This bring about new concerns for the role of an architect; indeed, some view Agile and architecture to be in conflict. Two of the original signatories to the Agile manifesto, Martin Fowler and Robert Cecil Martin, have been vocally opposed to this idea. Indeed, Fowler is clear in clarifying the fact that while the Agile manifesto is hostile to large upfront design (such as the type you see in Prince2), Agile does not reject upfront design itself.

The computer scientist, Allen Holub, has a similar view. Agile focuses on doing things that are important for delivering software that is useful to the user, ahead of software that is merely useful for the salesman. In order for software to be of use in the long term it must be adaptable, extendable, and maintainable.

Fowler also has a vision for an architect within software development teams. Citing the fact that irreversible software...