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

RESTful API design


Many developers use and build REST APIs without understanding what makes them RESTful. So what actually is REpresentational State Transfer? Moreover, why is it important that an API is RESTful?

There are some key architectural constraints to an API being RESTful, the first of these is being stateless in nature.

Stateless nature

RESTful APIs are stateless; the client's context is not stored on the server between requests.

Suppose you create a basic PHP app that has login functionality. After validating the user credentials that are put into the login form, you may then go ahead and use a session to store a state of the logged in user as they proceed to their next state to carry out the next task.

This is unacceptable when it comes to a REST API; REST is a stateless protocol. The ST in REST stand for State Transfer; the state of a request should be transferred around rather than merely stored on the server. By transferring sessions instead of storing them you avoid having sticky...