In Bagisto, 30 of its 42 packages depend on each other in a single group. You cannot change one of them without the others coming along. I measured four more open source Laravel apps split into modules. Every one has the same shape. The smallest group covers 53% of the modules. The largest covers 95%.
None of these apps is broken. They all work. This post is about something else: what folders do and do not do once a codebase grows.
What I measured
App Modules built with Modules In the big cycle group
Bagisto (e-commerce) namespaces in packages/Webkul 42 30 (71%)
Advising App (student advising) InterNACHI/modular 37 29 (78%)
LaravelEcomm (e-commerce) nwidart/laravel-modules 29 25 (86%)
Krayin CRM (CRM) namespaces in packages/Webkul 20 19 (95%)
Leantime (project management) plain folders in app/Domain 45 24 (53%)
A "cycle group" is a set of modules where each one depends on all the others, directly or through the chain. If Sales uses Shop and Shop uses Sales , they form a group of two.…