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


In this chapter, we created an entire toy MVC system and proved that it works through the use of some automated testing. Rather than follow the order of naming in MVC, we started by looking at the Controller layer, and we implemented a front controller that handles dispatching requests to the correct controller.

Next, we built our Model layer. For the purposes of the toy, we are using hard-coded data and not using any kind of persistence layer. In real life, you would never do this and instead would expect to be interacting with some form of persistence (most usually a database). We looked at the Entity, Repository, and Collection patterns. We were using a UUID for IDs, which is definitely something I would encourage you to consider as a much better ID than simple integer IDs and relying on database autoincrement values.

Next, we built our View layer. We used a DTO to handle storing and sharing template data – this keeps our View layer nicely decoupled from the...