|
|
|
|
|
|
by ecuaflo
1265 days ago
|
|
|
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 |
|
|
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