3 ms·
I've always found the best cloud path to stick with basic VM/VPS offerings, blob storage, DNS, CDN and IdP. Getting into things like functions as a service has
by bob1029 2y ago
I've always found the best cloud path to stick with basic VM/VPS offerings, blob storage, DNS, CDN and IdP.
Getting into things like functions as a service has always felt a little too hot for me. I don't mind integrating with cloud services though (e.g. S3-compatible APIs).
Hybrid seems to be most compelling if you can keep the monster in the box. Sign up for something like Azure or AWS to get at their IdP, DNS and CDN but keep all your actual machines in a cheaper provider (hetzner, et. al.).
- acdha 2y agoMy rule is to use services which could easily be replaced. For example, on AWS using RDS is a gimme because you can always spin up your own database with the same engine but not having to spend months building the equivalent battle-tested configuration is a pure win. ECS Fargate is great because you can run containers for at one order of magnitude lower ops investment than Kubernetes but if you had to leave, it’s vanilla containers on Linux. Something like DynamoDB, though, I’d want to think about what a migration plan would look like since databases are core to your application but the semantics are not as interchangeable as SQL databases are.