5 ms·

Was it a business or technical decision to do multi-cloud? Did you run simultaneously in 3 clouds? Can you explain the setup? If not, did you do just run on e

Was it a business or technical decision to do multi-cloud? Did you run simultaneously in 3 clouds? Can you explain the setup? If not, did you do just run on each for a while to test, or have a reason to switch? This is probably an impossible question to answer, but: were the savings/benefits of doing this actually worth the engineering costs involved in the end? Eg even if you chose what turned out to be the most expensive, worst option, would the company ultimately have been in a better place by having engineering focused on building things to increase customer value instead?

yonixw 5y ago
> Was it a business or technical decision to do multi-cloud? > Did you run simultaneously in 3 clouds? Can you explain the setup? The solution itself could be running on a single cloud. But we work in the finance sector and targeting highly regulated clients. And we got a tip very early on, that each client could ask for deployment on their cloud account that is monitored by them. Which will probably be AWS or Azure. Today we know only some require that. So it helped somewhat. > were the savings/benefits of doing this actually worth the engineering costs involved in the end? Like you said, very hard to know. In our case, we had a DevOps Cloud guy working a full time job, so, it was not noticeable. Reason being, Probably, [1] Because although he had problems to solve on all clouds, clouds deployments eventually get stable enough, So pressure was spread. [2] Although all clouds still need constant maintenance, it's a-synchronic (you can't plan ahead when AWS EKS K8s will force a new version), so pressure was spread out and it never stopped client feature building. But who knows, maybe for other architectures or a bigger company, it would have become noticeable.

5 ms·

Was it a business or technical decision to do multi-cloud? Did you run simultaneously in 3 clouds? Can you explain the setup? If not, did you do just run on e

by gregmac 5y ago

yonixw 5y ago
> Was it a business or technical decision to do multi-cloud? > Did you run simultaneously in 3 clouds? Can you explain the setup? The solution itself could be running on a single cloud. But we work in the finance sector and targeting highly regulated clients. And we got a tip very early on, that each client could ask for deployment on their cloud account that is monitored by them. Which will probably be AWS or Azure. Today we know only some require that. So it helped somewhat. > were the savings/benefits of doing this actually worth the engineering costs involved in the end? Like you said, very hard to know. In our case, we had a DevOps Cloud guy working a full time job, so, it was not noticeable. Reason being, Probably, [1] Because although he had problems to solve on all clouds, clouds deployments eventually get stable enough, So pressure was spread. [2] Although all clouds still need constant maintenance, it's a-synchronic (you can't plan ahead when AWS EKS K8s will force a new version), so pressure was spread out and it never stopped client feature building. But who knows, maybe for other architectures or a bigger company, it would have become noticeable.