Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

finacoles2's avatar

Which is better? laravel as a backend server or as platform to host both the backend and frontend?

Say you want to develop a coursera like application, with every college has its own subdomain and content (multi-tenancy).

I wonder what would option would you choice to increase the simplicity, scalability, and maintainability of your project.

A. have to separate codebase/server or

B. have a single codebase/server from both the frontend and backend.

0 likes
4 replies
bugsysha's avatar

If I'm alone on the project, option B. If it is a bigger team, probably A. There is nothing wrong with monoliths that are written properly.

martinbean's avatar

I wonder what would option would you choice to increase the simplicity, scalability, and maintainability of your project.

A. have to separate codebase/server

@finacoles2 If you want simplicity and maintainability, then why on earth would you consider doubling the number of codebases you have to maintain, deploy, and scale?

finacoles2's avatar

Say you want to develop a coursera like application, with every college has its own subdomain and content (multi-tenancy). https://1921681254.mx/

I wonder what would option would you choice to increase the simplicity, scalability, and maintainability of your project. https://100001.onl/

A. have to separate codebase/server or

B. have a single codebase/server from both the frontend and backend. issue got solved

martinbean's avatar

FFS. Yet another user that’s posted a thread, only to come back days later and re-post the original question but with spam links peppered in.

@jeffreyway, I think there’s a real need for creating a spam filter that checks for this behaviour. I’m beginning to feel that there’s really no point in contributing if the “questions” being asked are in fact just spammers trying to get some Google juice.

1 like

Please or to participate in this conversation.