4 ms·

But why would you try to build something cloud-agnostic to run on the most cloud-aware tier: serverless? Computers don't come forth from the ether, your code is

But why would you try to build something cloud-agnostic to run on the most cloud-aware tier: serverless? Computers don't come forth from the ether, your code is always running _somewhere_ and serverless means your provider makes a ton of choices for you. The lowest common denominator across clouds is a VM. If you can run your applications and your databases on VMs, you can run them on any cloud AND on-premises. If you can't run CosmosDB or AWS Whatever on a VM, your choice of DBMS/ORM doesn't affect that you're tied to that cloud provider.

galaxyLogic 4y ago
I wonder could micro-services be the solution? Run some of your micro-services on AWS and another on Azure etc. A given micro-service then might be highly dependent on AWS but the part of your application that uses those micro-services would not know anything about internals of AWS etc.
- guhidalg 4y ago
  Perhaps if you're trying to get the best products from each cloud, but I doubt this would be worth it. For each cloud you are going to need to establish: accounts, payment, access control, continuous deployment, geographical locality of their DCs, distributed logging, billing (and watch out for egress costs!), etc... I cannot imagine the added complexity of doing this would overcome the benefits of doing everything with one provider. But hey if your goal is to bill a client as much as possible by claiming that you're using the best products from each cloud, this sounds like a GREAT business idea.
  - galaxyLogic 4y ago
    Maybe not so much to get the best product out of each but to isolate the dependencies behind micro-service interfaces. Make comparisons and if one provider seem to be clearly the cheapest yet good enough then move more services to them. SEE also: https://levelup.gitconnected.com/how-we-reduced-our-annual-server-costs-by-80-from-1m-to-200k-by-moving-away-from-aws-2b98cbd21b46 https://levelup.gitconnected.com/how-we-reduced-our-annual-s...
emacdona 4y ago
Agree that lowest common denominator is a VM. But... I'm curious: has anyone here made an attempt to go "cloud-agnostic" by targeting managed kubernetes offerings? (GKE, EKS, AKS). Just curious how much pain I'd be causing myself if I ever attempted it ;-)

galaxyLogic 4y ago

I wonder could micro-services be the solution? Run some of your micro-services on AWS and another on Azure etc. A given micro-service then might be highly dependent on AWS but the part of your application that uses those micro-services would not know anything about internals of AWS etc.

guhidalg 4y ago
Perhaps if you're trying to get the best products from each cloud, but I doubt this would be worth it. For each cloud you are going to need to establish: accounts, payment, access control, continuous deployment, geographical locality of their DCs, distributed logging, billing (and watch out for egress costs!), etc... I cannot imagine the added complexity of doing this would overcome the benefits of doing everything with one provider. But hey if your goal is to bill a client as much as possible by claiming that you're using the best products from each cloud, this sounds like a GREAT business idea.
- galaxyLogic 4y ago
  Maybe not so much to get the best product out of each but to isolate the dependencies behind micro-service interfaces. Make comparisons and if one provider seem to be clearly the cheapest yet good enough then move more services to them. SEE also: https://levelup.gitconnected.com/how-we-reduced-our-annual-server-costs-by-80-from-1m-to-200k-by-moving-away-from-aws-2b98cbd21b46 https://levelup.gitconnected.com/how-we-reduced-our-annual-s...

emacdona 4y ago

Agree that lowest common denominator is a VM. But... I'm curious: has anyone here made an attempt to go "cloud-agnostic" by targeting managed kubernetes offerings? (GKE, EKS, AKS). Just curious how much pain I'd be causing myself if I ever attempted it ;-)