SWPatterns.com

Microservices - PHP

The Microservices pattern structures an application as a collection of loosely coupled, independently deployable services, built around specific business capabilities. Each service owns its data and communicates with others typically via lightweight mechanisms like HTTP. This example simulates a simple e-commerce …

N-tier - PHP

The N-tier pattern organizes an application into distinct layers, each with a specific responsibility. This promotes separation of concerns, making the application more maintainable, testable, and scalable. A typical N-tier architecture includes a presentation tier (UI), a business logic tier, and a data access tier. …

Client-Server - PHP

The Client-Server pattern decouples a service provider (server) from its consumers (clients). The server provides resources or services, while clients request and utilize them. This promotes modularity, allowing the server to be updated or scaled independently of clients. Our PHP example simulates a simple time server. …

Self-contained Systems - PHP

The Self-Contained System pattern advocates for building independent, deployable units of functionality within a larger application. Each system manages its own dependencies and data, minimizing external coupling. This fosters resilience, testability, and independent development/deployment.

The code demonstrates a …

Monolith - PHP

The Monolith pattern represents a traditional software architecture where all functionalities are tightly coupled and deployed as a single, indivisible unit. This example showcases a simple PHP monolith handling user registration and basic greetings. All related code – database connection, user handling, and view …

Microkernel - PHP

The Microkernel pattern aims to create a small, core system that provides minimal functionality, with additional features implemented as plugins or extensions. This fosters modularity, flexibility, and testability. The core handles only essential tasks, delegating everything else.

This PHP example implements a basic …

Clean Architecture - PHP

The Clean Architecture pattern separates the application into concentric layers: Entities, Use Cases, Interface Adapters, and Frameworks & Drivers. The core business logic (Entities & Use Cases) is independent of external concerns like databases, UI, or frameworks. This promotes testability, maintainability, …

Onion Architecture - PHP

The Onion Architecture aims for loose coupling by organizing code in concentric layers. The core layer contains business rules and entities, independent of any infrastructure. Surrounding layers handle interface adapters (like controllers) and infrastructure details (databases, UI). Dependencies point inward – …

Hexagonal Architecture - PHP

The Hexagonal Architecture (also known as Ports and Adapters) aims to create loosely coupled software by decoupling the core application logic from external concerns like databases, UI, or third-party services. This is achieved by defining ports – interfaces that the core uses to interact with the outside world – and …

Layered Architecture - PHP

The Layered Architecture pattern organizes an application into distinct layers, each with a specific responsibility. This separation concerns allows for easier maintenance, testing, and modification – changes in one layer ideally don’t affect others. Common layers include Presentation (UI), Application (Business …