This lines up with how I have chosen in client work. The question I ask first is who maintains it in year two, not which one ships the MVP faster. For a CRUD heavy SaaS with an admin side, Laravel has saved me the most time because auth, queues and scheduled jobs arrive as one tested set instead of five libraries I have to wire together. I would only pick NestJS when the team already writes TypeScript everywhere and real time features are central, not just nice to have.
Thanks Kamran, "who maintains it in year two" is a better first question than the one I led with. It also makes the hand-over easier: one framework's auth, queues and scheduler are simpler for the next developer to pick up than five libraries wired together by hand. In the post's Driveway Morocco example (a car-rental demo I built in Laravel), adding the Expo mobile app later only meant adding Sanctum tokens to the same backend, with no second server. When you do pick NestJS, do you keep real-time inside the main app or split it into its own service from day one?
Kamran Khan
Full-Stack Web Developer (React.js + Laravel) | Dashboards, SaaS Apps & Management Systems for Global Clients
This lines up with how I have chosen in client work. The question I ask first is who maintains it in year two, not which one ships the MVP faster. For a CRUD heavy SaaS with an admin side, Laravel has saved me the most time because auth, queues and scheduled jobs arrive as one tested set instead of five libraries I have to wire together. I would only pick NestJS when the team already writes TypeScript everywhere and real time features are central, not just nice to have.