apiato VS laravel-modules

A framework over Laravel for big web app: https://github.com/apiato/apiato

Oh you mean Domain Driven Design, you can do that in Laravel. I worked on plenty of projects who did it like that. You can even find packages for that, like this one https://github.com/nWidart/laravel-modules.

I recommend using this package https://github.com/nWidart/laravel-modules makes building with modules easier.

We recently changed our repository with using https://github.com/nwidart/laravel-modules

There are a bunch of options, we started with Domain Driven Design which I like since it organizes things while still allowing for core laravel. But you need to answer some questions first like will you support/handle multi tenancy? if so, how? Do you want features like Single Sign On? And so on. No need to answer me, thats for you to answer yourself as it may impact your layout decisions. After doing some work with the Laravel modules package from nWidart (https://github.com/nWidart/laravel-modules), there are some things I really like in there as well, which I kind of wish I had used that first. We're too long in the tooth so to speak to migrate over, and I haven't answer all my questions for that, such as how that handles vue.js, it seems very blade centric and we don't use blade at all in our app. But having a Modules folder with all of the bits from controllers, models, views, etc contained is very nice. In your case I would do some research on those things and what others here have suggested. One of the hardest things no one talks about is maintaining a large app as it grows in scope and creep. Implementing strong organization up front can be a huge help.

I totally agree with this, but I’d like to mention an exception. I found using nWidart’s laravel-modules library highly useful as a utility for creating and interacting with individual modules, as well as the ability to customise the stubs that generates them.

i'm trying to edit an existing application which it's using this package and what i want is to add the SaaS module for this application and also have a dynamic subdomain that depends on the company that want to buy this product..;

For a typical Laravel application, you could leverage namespaces, service providers, autoloaders, packages, API routes to totally separate these modules. There is a package that could help with this. Check it out here: nwidart/laravel-modules.

If you find your project is getting truly large, you could always explore breaking the entire codebase into modules: https://github.com/nWidart/laravel-modules