Hey everyone I created MDA to solve a real problem in my company: developers organizing code differently across projects (some used repositories, others put everything in controllers, some tried DDD halfway...).

What is MDA?

An opinionated starter kit that organizes Laravel projects around models, with clear separation:

Actions, Finders, Queries, Repositories by model

Predictable flow: Controller → Service → (Finder/Query/Action)

Flexible, not dogmatic - adapt it to your needs

What it's NOT: Full DDD or "the right way" - just a practical guide for team consistency. Why share this? I know there's much I still need to learn. I'd love your feedback:

What problems do you see? What would you improve? How have you solved similar issues?

Docs: zangles.github.io/MDA/README.en

Thanks for your time!

A good approach. Some have tried DDD but only halfway through, which is correctly pointed out. However, is it still too complex? Would it be faster if we only used the Repository pattern and DTOs, rejecting the encapsulation of complex queries and replacing them with multiple simple queries, using them as needed to avoid an explosion of query objects? But a more pressing concern is how to elegantly apply this in Filament. The Repository pattern and DTOs are definitely suitable for splitting a task between two AI agents, allowing both agents to operate without concerning themselves with each other's specific behaviors.