Book Image

The Art of Modern PHP 8

By : Joseph Edmonds
5 (1)
Book Image

The Art of Modern PHP 8

5 (1)
By: Joseph Edmonds

Overview of this book

PHP has come a long way since its introduction. While the language has evolved with PHP 8, there are still a lot of websites running on a version of PHP that is no longer supported. If you are a PHP developer working with legacy PHP systems and want to discover the tenants of modern PHP, this is the book for you. The Art of Modern PHP 8 walks you through the latest PHP features and language concepts. The book helps you upgrade your knowledge of PHP programming and practices. Starting with object-oriented programming (OOP) in PHP and related language features, you'll work through modern programming techniques such as inheritance, understand how it contrasts with composition, and finally look at more advanced language features. You'll learn about the MVC pattern by developing your own MVC system and advance to understanding what a DI container does by building a toy DI container. The book gives you an overview of Composer and how to use it to create reusable PHP packages. You’ll also find techniques for deploying these packages to package libraries for other developers to explore. By the end of this PHP book, you'll have equipped yourself with modern server-side programming techniques using the latest versions of PHP.
Table of Contents (19 chapters)
Section 1 – PHP 8 OOP
Free Chapter
Chapter 1: Object-Oriented PHP
Section 2 – PHP Types
Chapter 5: Object Types, Interfaces, and Unions
Section 3 – Clean PHP 8 Patterns and Style
Section 4 – PHP 8 Composer Package Management (and PHP 8.1)
Section 5 – Bonus Section - PHP 8.1


The View represents the visual output that the application provides in response to a particular request. In most modern frameworks, the View layer includes a templating language that is designed to be frontend-developer-friendly, optimized for working on HTML and outputting safely escaped data. For the toy, we are sticking with plain PHP, though I have included a simple output escaping system.

The first thing that our app has to do is prepare the template data. I have kept the template data as a separate DTO, which is a pattern I encourage as it really helps to keep things organized. All template data implements a specific interface. Actually, the interface has no behavior in the toy – that is not an issue – but it does give us the option of enforcing standardized behavior later on, should we choose to.

What is a DTO again?

DTO stands for Data Transfer Object. It is simply an object that has no behavior and whose sole purpose is to be instantiated with data...