Not bad. 1st part of the book is about 4 design patterns and SOLID principles. 2nd part of the book is an example of billing app: first in ZF2, then it switches to Laravel.
A great book that explains the Clean arch. with an implementation example removing the code gap problem. Some points would be better to be considered: 1. I had to go through some misconfigured framework configurations to get it up and running. 2. Should provide frameworks and libraries versions to match the same environment as the frameworks had evolved and the file structure had changed a bit. 3. What about the ActiveRecord that most frameworks use be default and is more popular than the DataMapper pattern?.
Замечательная книга, которая расставляет всё по полочкам. Рассказ начинается с самых азов программирования PHP и постепенно показывает как получить приложение, которое соответствует чистой архитектуре (луковому варианту). Лучше читать издание 2016 года, там часть с примерами более полная. Также код примера эволюции приложения между фреймворками и инструментами приведён на github, удобно уточнять непонятные места. Советую прочитать всем, кто задумался над правильной архитектурой. Самое главное что я вынес из книги -- это мотивация следовать чистой архитектуре. Ранее возникали мысли, что это бесполезное занятие достойное разве что энтерпрайзной джавы. НО! как показывает учебный пример полезно и в PHP. Хотя пример и выглядит неубедительно, но это из-за куцей модели предметной области.
The book explanation sequence to preview the bad code issues and the gradually improvements with every chapter in the same code is very clear and make it easy to understand.
The only problem with the book that it is too old, so there are deprecated technologies used in the explanation, I found it difficult and very time consuming to try using laminas instead of Zend Framewrok which the author used to explain code framework independence but it is very good as a begging to understand architecture.
I think this book is a must to read for every PHP Developer to enhance his/her code. the first 100 pages were really fascinated and very helpful to understand more about clean code and applying solid and achieving dependency to each layer of your code.
I read this book around 3 times till now - some of the topics I read more than 3 times.
Take your time to grasp the concepts first, the implementation is super easy after deep understanding.
I would recommend this book to developers of any level, who want to produce good, clean and solid code. I like the way that the author explains everything, clear and interesting. I also particularly like how he splits the M - Model in MVC architecture into Entity and Persistence.