[brundolf]

> But many of those are just not as reliable as core cloud providers

Aren't they? I've never heard this, do you have a source?

> the cost is way higher

Depends. For small-medium stuff the cost may be "way higher" in that it's dollars instead of pennies per month, but you have to weigh that cost against the cost of your time (how many months of PaaS hosting did the past week cost you in dev hours?). I'm sure the economics become significant at some scale, but I'd ask yourself whether they are at your scale

> and now you’re setting up a local stack that probably wildly differs from how it will work in production between those services

That doesn't have to be true at all; many of these services let you ship Docker containers if you want to (and manage everything else from there), but it's possible to go without even that: https://news.ycombinator.com/item?id=34243045

I'd recommend taking a step back and seeing how much complexity is really necessary for what you're trying to do

[ecuaflo]

There was actually just a thread about Fly and someone pointed out lots of outages https://news.ycombinator.com/item?id=34240679

I also meant this in the sense that you are locking yourself into very immature companies that can shut down anytime the VC money stops. They are not proven like the core cloud services that the Fortune whatever companies all rely on. Also with those core cloud services being more low level, you are free to move between them much easier than the hyperpreconfigured 2nd tier serverless services.

I’m certainly not familiar with all the providers. Maybe there is one I haven’t found yet that would be a better fit

[brundolf]

> with those core cloud services being more low level, you are free to move between them much easier than the hyperpreconfigured 2nd tier serverless services

I actually think it's the exact opposite

With the big providers you can create elaborate architectures that pull together a bunch of hyper-specific services, or if you do everything bare-metal, you have to write (again, elaborate) configurations in terraform or whatever else

With a PaaS, your contract with the platform is usually very simple by design: "download the code and run this command", or "expose a postgres DB", or "serve these files". Because the contract is so simple, it's very easy to run the same stuff locally on your dev machine, or move it to another provider. Because it doesn't care about what architecture it's running on, it doesn't care about what platform it's running on

It's the same as with programming languages: if you write something in assembly, its contract with the host system is very broad, which means it's tightly coupled to the OS and the chip architecture. If you write something in Java - a higher abstraction level - it can be run on anything under the sun, because it cares very little about the details of the environment it's running in