5. Behavioral Design Patterns | Mastering PHP Design Patterns

Sign In Start Free Trial

Book Overview & Buying
Table Of Contents

Mastering PHP Design Patterns

By : Junade Ali

1.5 (2)

Mastering PHP Design Patterns

1.5 (2)

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.

Preface

Preface

What this book covers

What you need for this book

Who this book is for

Conventions

Reader feedback

Customer support

Free Chapter

1. Why "Good PHP Developer" Isnt an Oxymoron

1. Why "Good PHP Developer" Isnt an Oxymoron

Coding style - the PSR standards

Revising object-oriented programming

Setting up the environment with Composer

The Gang of Four (GoF)

Summary

2. Anti-Patterns

2. Anti-Patterns

Why anti-patterns matter

Not invented here syndrome

God objects

Environment variables in PHP source

Singletons (and why you should be using dependency injection)

Database as IPC

Auto-increment database IDs

Cronjob imitating service

Software in place of architecture

Interface Bloat

Cart before the horse

Separation of development and operations

Excessive separation of development responsibilities

Error suppression operator

Blind faith

Sequential coupling

The big rewrite

Tester-Driven Development

Bloated optimization

Uneducated manager syndrome

Wrong rocky foundations

Long methods

Magic numbers

Summary

3. Creational Design Patterns

3. Creational Design Patterns

Software design process

Simple Factory

Factory Method

Abstract Factory pattern

Lazy initialization

Builder pattern

Prototype pattern

Summary

4. Structural Design Patterns

4. Structural Design Patterns

Agile software architecture

Decorator

Adapter

FlyWeight

Composite

Bridge

Proxy pattern

Facade

Summary

5. Behavioral Design Patterns

5. Behavioral Design Patterns

Personality traits for passionate programmers

Observer pattern (SplObserver/SplSubject)

Iterators

Generators

Template Method design pattern

Chain of Responsibility

Strategy design pattern

Specification design pattern

Scheduled Task pattern

Summary

6. Architectural Patterns

6. Architectural Patterns

Model-View-Controller (MVC)

Service-oriented architecture

Microservices

Asynchronous queueing

Summary

7. Refactoring

7. Refactoring

What is refactoring?

Test, test, and test again

Code smells

What do I tell my manager?

Summary

8. How to Write Better Code

8. How to Write Better Code

Nature of a HTTP request

RESTful API design

When in doubt – KISS

Software development life cycle

On Scrum, and real Agility

You need to sack people sometimes

Lean project management

YAGNI and defering decisions

Monitoring

Tests fight legacy

Behavior-Driven Development

Summary

Chain of Responsibility

Suppose we have a group of objects that together are meant to solve a problem. When one object can't solve a problem, we want the object to send the task to a different object in a given chain. This is what the Chain of Responsibility design pattern is used for.

In order to get this to work, we need a handler, which will be our Chain interface. The various objects in the chain will all implement this Chain interface.

Let's start with a simple example; an associate can purchase an asset for less than $100, a manager can purchase something for less than $500.

Our abstraction for the Purchaser interface looks like this:

<?php 
 
interface Purchaser 
{ 
  public function setNextPurchaser(Purchaser $nextPurchaser): bool; 
 
  public function buy($price): bool; 
}

Our first implementation is the Associate class. Quite simply, we implement the setNextPurchaser function so that it will set the nextPurchaser class property to the next...

Visually different images

CONTINUE READING

83

Tech Concepts

36

Programming languages

73

Tech Tools

Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.

Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.

50+ new titles added per month and exclusive early access to books as they are being written.

Mastering PHP Design Patterns

Search

Your notes and bookmarks