come back when you have millions of users
#premature_optimisation
Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.
Is it true that an application in laravel + vue js + inertia.js is poorly scalable in terms of monthly server costs? So compared to serverless? How can I make a Laravel+ vue.js + inertia.js application scalable to millions of users per day and keep server costs low? Also, are there simple managed solutions so I don't have to be familiar with certain things?
Is it true that an application in laravel + vue js + inertia.js is poorly scalable in terms of monthly server costs?
@kuechenplaner Says who? 🤷♂️
So compared to serverless? How can I make a Laravel+ vue.js + inertia.js application scalable to millions of users per day and keep server costs low?
People need to stop thinking “serverless” is some magic bullet for both scalability and cost. It’s not. You get charged per invocation. If you do get “millions of users per day” then your costs are going to rise along with your workload. Unlike if you just rented a VPS or similar for a fixed price per month.
Also, are there simple managed solutions so I don't have to be familiar with certain things?
Well, if your goal is to keep server costs down then a managed solution is just going to add to that cost, as you not only have to pay for the underlying server/resources, but then also pay whatever company is managing the solution for you.
My client wants it to be scalable to so many users, not me.
Doesn’t change the fact that this is classic premature optimisation. Solve problems when you actually have them, not before. When you try and guess the problems you’ll have with scale, you’ll always be wrong. You try and optimise for X, reality will laugh in Y.
Please or to participate in this conversation.