2 ms·
I very recently have built a multi-cloud empire of machines, effectively, and from my experience it is best to build for each cloud one at a time. The differenc
by busterarm 6y ago
I very recently have built a multi-cloud empire of machines, effectively, and from my experience it is best to build for each cloud one at a time. The difference here is you have the day 1 assumption that you will be on all clouds and you don't lock yourself into vendor-specific features and make sure your platform can run anywhere with no functional differences to your users.
- ZeroCool2u 6y agoThat's fair and totally makes sense from the perspective of someone that is able to enforce that assumption. In my experience in large orgs that condition is very difficult to enforce and that's when organizational inertia kicks in. But your method is objectively better if you can prevent people from doing dumb stuff while you keep working.
- busterarm 6y agoWe handled it by spinning up everything via terraform and forcing dependency on those modules & resource bundles. Separate sets for each cloud provider and it all gets code reviewed by one team. Essentially we built a platform on top of each cloud. The difficulty there is groking the differences in network topology and access control and building something functionally equivalent everywhere.