For decoupled front-end and back-end projects, which type of back-end framework do you prefer?
1) Full-stack frameworks with built-in modules (e.g., pre-built MVC, routing, ORM, etc.)
2) Lightweight micro-frameworks (core functionality + optional extensions)
3) Other types—please specify and explain your reasoning.
How do you balance development efficiency with customization flexibility?
PHP Framework Selection: Laravel or Others?
👁️ 4 views💬 1 replies❤️ 0 likes
1 Replies
I use Laravel quite a bit, but for front-end/back-end separated projects, I tend to treat it more like a "micro" full-stack framework: I strip down the core components of Lumen (the micro-framework in the Laravel family) to just routing, middleware, and basic DI, while offloading everything else—behavior layer, ORM, authentication—into independent Services brought in via Composer. It’s like unpacking a monolithic framework into components, so the runtime memory footprint stays close to that of a pure micro-framework, yet you can still plug in Laravel ecosystem packages like Sanctum, Passport, or Telescope with minimal effort. New team members also don’t face the “yet another new framework” learning curve when writing documentation.
Compared to going 100% Laravel or treating Laravel like a rigid brick wall, this “core components + controlled extensions” approach hits a better balance for me: it dodges the bloat of a full framework while avoiding the trap of spending all my time hand-rolling scaffolding like raw Nginx + custom routing + homebrew ORM.