4 ms·
And there's not a way to remove the egress pricing moat because it's so natural. Of course it costs less money to move data within a datacenter than outside of
by pradn 6y ago
And there's not a way to remove the egress pricing moat because it's so natural. Of course it costs less money to move data within a datacenter than outside of it. So, why wouldn't it cost less to do everything inside AWS? Egress pricing is probably multiples of this actual discrepancy to erect the moat even deeper.
It really does feel hopeless to run an open-source service that isn't running on an existing crowd. Perhaps that's one reason Snowflake is doing well.
- boulos 6y agoSee my sibling comment. Snowflake actually has historically run as a multinenant service with access to say your S3 bucket, so the majority of data transfer is VM <=> S3 in the same Region (so included/free). As a snowflake customer, you would submit queries (and data ingestion) as Egress pricing (roughly $.01/GB though assuming it was using the private link or similar) and then the smallish results come back as Ingress (which AWS charges for, we do not, but whatever). I hope someone corrects me on the AWS side (I really thought that there was a way to do zero rating for same “AZ” third-party services), but it’s not fundamental.
- sandGorgon 6y agono this is not free. Because what you would do is setup a "peering" between Snowflake cluster and your own. Even if it is the same region, there is a cost - https://docs.aws.amazon.com/vpc/latest/peering/vpc-peering-basics.html https://docs.aws.amazon.com/vpc/latest/peering/vpc-peering-b... That cost acts as a barrier if AWS launches its own Snowflake competitor. Basically AWS taxes you for not using other AWS services, once you are inside AWS.
- pradn 6y agoThis doesn't get around the egress pricing for sending data from AWS to another company's data center, yes?