Serverless seems great to me. But it can be very expensive.
The best analogy is ZipCar vs. Buy a car.
Owning or leasing a car is cheaper than ZipCar if you compare the hourly rates.
But, if you only use car occasionally, then owning a car (or even leasing a car) get more expensive, since it is sitting around doing nothing a lot of the time.
It really depends on what the traffic pattern of your application looks like. For most web applications, traffic can be unpredictable. Instead of paying for idle compute time during low traffic periods (where you waste money on unused compute resources), you can simply pay-what-you-use with serverless: the infrastructure only exists when there is an incoming request.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.