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

Microservices


A microservices architecture can be considered a subset of service-oriented architectures.

Fundamentally, microservices form complex applications by composing them of small independent process which intercommunicate over a language-agnostic API that makes each services accessible to each other. Microservices can be individually deployed as services.

In microservices, the business logic is separated into self-contained loosely-coupled services. A key tenet of microservices is that each database should have their own database, which is vital to ensure that the microservices do not become tightly coupled to each other.

By reducing the complexity of a single service, we can aim to reduce the amount of points at which this service will fail. In theory, by having a single service comply with the Single Responsibility Principle, it is easier to debug and reduce chances of failure in our application as a whole.

In computer science, the CAP theorem dictates that it is impossible to guarantee...