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

Dependency injection and the service locator

Something you may have realized when looking at ToyMVC is the fact that there is quite a lot of work going on to build instances of objects. Also, you could imagine that if the app grew to real-world sizes, then the amount of work that would need to be done in AppFactory could become quite substantial.

Furthermore, due to the complexity of building up a large graph of object instances, there is also the issue that this is generally going to be very wasteful. PHP's requests are not stateful and when instantiating an MVC app, it is almost certain to serve one – and only one – request. There is no need to fire up instances of every single piece of the application when we may not need them all.

Thankfully, there is now a widely accepted best practice solution for this that is incredibly developer-friendly – dependency injection, or DI for short.

Now, I say this is developer-friendly, but that does not mean...