Several things I don't like in this boilerplate

[inkuber]

Several things I don't like in this boilerplate

[jorge07]

Hey @inkuber

1 - You're totally right. I use to develop very small services and for those this layered structure just works. For bigger ones I flip the structure the same way: BoundedContext/Layers. On the other hand Identity and access management use to be a supporting subdomain inside a bigger one like Customer/Members.
2 - This really depends of your business model, what works for you may not work for others. An specification pattern allows you to define different rules decoupling the implementation. Sometimes works, sometimes it's just too much for the task. So IMO here, it depends.
3 -Yes, not all your business must implemented as ES, but probably the opposite. On the other hand usually User it's core business and this boilerplate illustrate with this example how to implement it. Nothing stops you from CRUD your business here.

I really appreciate your feedback. Seriously thinking about flip the layered structure so you don't have to when projects grow.

[jorge07]

After upgrade to PHP 8 yesterday I finally decided to go and switch to bounded context first structure. WIP