4 ms·
The most obvious one is exclusive products or features that only exist within a single cloud provider. Binding your scripts to a non-standard API will complica
by _jplc 4y ago
The most obvious one is exclusive products or features that only exist within a single cloud provider.
Binding your scripts to a non-standard API will complicate any migrations outside of it and involve a lot of work. (example: Migrating away from Azure Resource Manager templates).
AWS outbound data is expensive. That complicates any data migration outside of AWS or communication between machines inside and outside AWS (example: Cheaper machines on another infrastructure provider with a lot of data transfers with AWS machines).