Hey Laravel devs, a question! 👋
For big projects containing a presentation website + app + ..., do you go full monolith or do you create separate Laravel repos for each part (and if so, how do you deal with repeated models, jobs, etc.)?
I'm a fan of the monolith. It's just so nice to have everything together and then you don't have to deal with separate hosting set ups either.
That's one of the main reasons I was thinking about in favor of the monolith. However, working as a team, separate repos could maybe offer less compatibility issues or maintenance overhead, allowing to upgrade each part at its own pace.
Ah, didn't realize you had separate teams. In my experience, I haven't found maintainability to be the issue–you just have branches for upgrades and it works out.
That said, if you have frontend devs who are used to working in JavaScript frameworks, there is a learning curve for them to step into a Laravel project. But, if you spend a week helping them get set up, then most of them are good to go pretty quickly.
