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

Monitoring


Monitoring systems become critical as you scale. Effective monitoring can drastically ease the maintenance of services.

Having spoken to multiple experts in this field, this is the advice I have collected on the subject:

  • Choose your key statistics carefully. Users don't care if your machine is low on CPU but they do care if your API is slow.

  • Use aggregators; think about services, not machines. If you have more than a handful of machines, you should treat them as an amorphous blob.

  • Avoid the Wall of Graphs. They are slow and it's information overload for a human. Each dashboard should have five graphs with no more than five lines per graphs.

  • Quantiles aren't aggregable, they're hard to get meaningful information from. However, averages are easy to reason. A response time of 10 ms in the first quartile isn't really useful as information, but a 400 ms average response time shows a clear problem that needs to be addressed.

  • In addition to this, averages are far easier to calculate than quantiles...