How makers stay productive

Serverless and containers are twos sides of the same coin, both tackling the same problem in different ways. It's not unrealistic to have a setup that takes advantage of both.

@lori It's true that AWS has everything you need but it's also overly complicated and has hidden costs. Both Vercel and Netlify are actually built ontop of AWS offering a simplified experience which I consider to be a good thing. Howewer you are totally right in that it means you have to depend on more external services to bridge the gaps. I think Serverless is actually cheaper starting out (but has a lot of synthetic hype built around it) and serverful is cheaper when you are getting consistently used.

But… My Backend needs a DB, and the offered options are not what I want to use. Also I will have Go or Python based Backend… So I anyway need at least for this 2 parts another service which makes then deployement not more the 1 push thing. Of course it's resolvable but the 20 bucks are not more resolving everything anyway. And Josh, yeah agree, Lambda ect have they use cases. And… for my other projects I anyway have a own server and pay much less I would pay using any cloud version.

Important: Last phrase/argument is really very particular and I would not say/do same thing in dayjob, at least not for any case. It's anyway never the case that one solution fits everything in best way. starts by programming lang, goes over DB to deployment/hosting etc :-)

I'm still not sold on serverless. I like Lambda for running things in certain scenarios but I'd never build an app that was deployed to serverless stuff.

My reasons are probably very particular. I do my first Next.js based project and vercel was first class option for this. And it really works very smooth. Makes sense :-)

It's an interesting discussion as on one hand the whole point of Serverless is pay what you use so when you have fixed plans it sort of defeats the point. On the other hand that 20 USD might actually be less in the long run when the pay what you use kicks in. I have had many internal battles trying to decide and settled with Vercel for now. Do you have any other reasons beside cost for the switch?

Are you starting a new project similar to Vercel?

no no :-) I just will handle deployment on my own using my existing infrastucture (Rancher 1.x & Docker), saving 20 USD