|
|
|
|
|
by scarface74
2228 days ago
|
|
Anticompetitive behavior when they clearly state the price? Of all the things that lock you in to any provider once you are at any scale, data isn’t the biggest one. If you have a massive amount of data, you can always get AWS to transfer it to you via a Snowball for $30/TB + a $300 fee. |
|
Giving you an option to only bulk egress is not the same either, since the most common scenario for egress would be operational day-to-day inter-network scenarios.
If there is an unreasonably high fee for exiting a provider's cloud, to any other network location, on an operational basis, it is actively discouraging exiting the provider's services creating a kind of price barrier that could be cost prohibitive for operational inter-networking.
Operational inter-networking, to me, encourages competition not discourages it.
For example, perhaps I want to use Microsoft Azure's Data Factory to move data from AWS S3 to Redshift. It is not possible as far as I know without egress from AWS to Microsoft's network, and then back again. But surely these clouds are connected with peering relationships making the cost of ingress/egress negligible, so why is this not allowed? That would allow users of the cloud to freely mix and match services from among many clouds.
The world I see today does not seem to encourage such competition.