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

Service-oriented architecture


Service-oriented architectures largely consist of business logic in services that communicate with data repositories.

These services can be derived in different forms to build applications. These applications adopt these services in different formats to build various applications. Consider the services as Lego blocks that can be put together to build an application in a given format.

This description is rather crude; let me clarify further:

  • Boundaries for services are explicit (they may separate web services on different domains, and so on.)

  • Services can inter-communicate using a common communication protocol (for example all use RESTful APIs)

  • Services are autonomous (they are decoupled and not related to another service in any way)

  • The message processing mechanism and the schema are understandable by every other microservice (and therefore are often the same), but the programming environment can be different

Service-oriented architectures are inherently distributed...