News for hackers. Stuff that matters.
Re:AWS’s Anti-Competitive Move Hidden in Plain Sight by daneel_w on Saturday March 18, 2023 @11:58AM (#35210132)
In my opinion there are better examples, such as how AWS' managed products are deliberately hobbled and handicapped to make it complicated to migrate away from them once you're in. Two examples that I have first-hand experience with:

It's easy to set Aurora up as "slave" for accepting replication data from an external MariaDB/MySQL server in order to make a smooth low-downtime migration into AWS, but there are... oddly peculiar kludges... when wanting to set Aurora up as "master" and have it feed its binlog outside in order to migrate away in the same smooth fashion.

For their managed Redis ("Elasticache") they have intentionally disabled a few functions that relate to exporting/migrating live data from one Redis instance to another. In particular the "MIGRATE" function, which is used specifically to make a fast and accurate dump of all data when you want to supplant (read: migrate) a Redis instance. Instead you have to hack manual outbound migration together yourself, key by key, database by database.

Re:AWS’s Anti-Competitive Move Hidden in Plain Sight by watermelon0 on Saturday March 18, 2023 @12:36PM (#35210541)
IMO these two examples might just be cases they were not optimizing for, and didn't want to invest engineering time (and future support) into something seldomly used.
Re:AWS’s Anti-Competitive Move Hidden in Plain Sight by georgyo on Saturday March 18, 2023 @01:20PM (#35211061)
They are seldomly used because they are difficult to use.

They are difficult to use because using them means loss of money.

Combined with other entrapping features means the all features that help escaping the ecosystem are seldomly used. So any individual products off boarding features are even less used.

These are also features that don't use more than once.

So of course when a product manager looks at usage metrics they see this feature is seldomly used and continue to deprioritize improving it.

Self-fulfilling prophecy.

Re:AWS’s Anti-Competitive Move Hidden in Plain Sight by User23 on Saturday March 18, 2023 @01:50PM (#35211405)
“Made it easier for customers to migrate to our competitors” isn’t a great look on your review.
Re:AWS’s Anti-Competitive Move Hidden in Plain Sight by veleek on Saturday March 18, 2023 @02:04PM (#35211532)
“Made our customers happy by allowing them to easily migrate to a self-hosted redis instance in AWS so they were able to build their business and brought in twice as much traffic”.

Your comment echos the crux of the article. Yes, this probably wasn’t an explicit goal for AWS, but the end result is that people aren’t using Amazon’s products because they’re the best, they’re just using them because it’s harder to change or more expensive not to (when it could be cheaper if the playing field was level).

Re:AWS’s Anti-Competitive Move Hidden in Plain Sight by TheNewsIsHere on Sunday March 19, 2023 @12:47PM (#35220870)
> Your comment echos the crux of the article. Yes, this probably wasn’t an explicit goal for AWS, but the end result is that people aren’t using Amazon’s products because they’re the best, they’re just using them because it’s harder to change or more expensive not to (when it could be cheaper if the playing field was level).

I think you hit the nail on the head, at least regarding my own experiences.

Most of the time when a colleague says “hey we can use X service because Y” in AWS, the “Y” is something along the lines of “because it’s just easier to use Z with it,” where “Z” is another AWS service.

AWS has many impressive tools. That doesn’t mean they’re built with friendliness in mind. Their tools are meant to provide value for money, but a lot of that value is predicated on using other tools they provide. They’re building a platform, not -your- platform.

We learned that lesson early on with my business. We ultimately replaced all but 2-3 AWS services with third parties that were actually best-in-class, and kept the 2-3 from AWS that AWS can honestly say are best in class. It was ultimately more expensive and kludgy to build everything on AWS rather than diversify our stack.

Re:AWS’s Anti-Competitive Move Hidden in Plain Sight by hobs on Saturday March 18, 2023 @03:26PM (#35212259)
When you see the same case across many cloud providers, data easy to get in and hard to get out, you start to get the point.
Re:AWS’s Anti-Competitive Move Hidden in Plain Sight by jzb on Saturday March 18, 2023 @03:43PM (#35212416)
It’s “data gravity,” as Dave McCrory put it a long time ago. Make it easy to put your data and workloads on a cloud, the “gravity” makes it hard to escape. The more you have the harder (more expensive) it is to break the pull.
Re:AWS’s Anti-Competitive Move Hidden in Plain Sight by dilyevsky on Saturday March 18, 2023 @04:56PM (#35213022)
See also: egress fees
Re:AWS’s Anti-Competitive Move Hidden in Plain Sight by daneel_w on Tuesday March 21, 2023 @07:56PM (#35254595)
It's not simply a case of more data = more work to migrate, which by the way is a fallacy in many cases. This is an artificial type of "gravity", because the migration procedure itself was hampered by deliberate disabling of the necessary tools.
Re:AWS’s Anti-Competitive Move Hidden in Plain Sight by daneel_w on Sunday March 19, 2023 @03:53PM (#35222866)
They invested engineering time into specifically removing these things and more.
Re:AWS’s Anti-Competitive Move Hidden in Plain Sight by lopatin on Saturday March 18, 2023 @12:33PM (#35210491)
What kinds of kludges are you referring to about reading Aurora binlog? I’ve been using Debezium to read the binlog to transition off of aurora and it works as expected.
Re:AWS’s Anti-Competitive Move Hidden in Plain Sight by durkie on Saturday March 18, 2023 @12:05PM (#35210201)
speaking of Elasticache -- I noticed that the "append-only file/AOF" feature for recovering from crashes/reboots is only available on AWS redis up to version 2.8.22, and we're now at like redis version 7 in the rest of the world..
Re:AWS’s Anti-Competitive Move Hidden in Plain Sight by daneel_w on Saturday March 18, 2023 @12:08PM (#35210231)
I'm convinced that, too, is disabled deliberately, in order to coerce you into buying one more overpriced Elasticache instance to use as fail-over. This type of "funneling" design pattern is recurring across their managed products.
Re:AWS’s Anti-Competitive Move Hidden in Plain Sight by cma on Saturday March 18, 2023 @12:09PM (#35210240)
Free ingress, expensive/hard egress.
Re:AWS’s Anti-Competitive Move Hidden in Plain Sight by daneel_w on Saturday March 18, 2023 @12:13PM (#35210271)
"The first one's on me, friend."
Re:AWS’s Anti-Competitive Move Hidden in Plain Sight by simplotek on Saturday March 18, 2023 @01:18PM (#35211024)
> Free ingress, expensive/hard egress.

Let's call AWS's "Free ingress, expensive/hard egress" business model as the AWS roach trap pattern.

Re:AWS’s Anti-Competitive Move Hidden in Plain Sight by marcosdumay on Saturday March 18, 2023 @01:40PM (#35211293)
"Roach trap pattern" is actually a great name.
Re:AWS’s Anti-Competitive Move Hidden in Plain Sight by bargle0 on Saturday March 18, 2023 @03:05PM (#35212089)
I’ve heard it called the Hotel California pattern.
Re:AWS’s Anti-Competitive Move Hidden in Plain Sight by charcircuit on Saturday March 18, 2023 @03:46PM (#35212441)
Pretty much every single network provider offers free ingress or egress. That is the industry standard pricing model for paying for bandwidth.
Re:AWS’s Anti-Competitive Move Hidden in Plain Sight by Uvix on Saturday March 18, 2023 @01:28PM (#35211154)
Both AWS and Azure's managed SQL Server database solutions are hobbled like that. They can be replication targets but not sources.

At least RDS for SQL Server lets you do native backup/restore, so while it's slow there's still a good way to get your data out. Azure SQL, you're stuck with something like the Elasticache solution. (Or theoretically BACPACs, but they aren't transactionally consistent and don't work for large databases.)

Re:AWS’s Anti-Competitive Move Hidden in Plain Sight by nova22033 on Saturday March 18, 2023 @01:42PM (#35211318)
You have the choice of running redis on an EC2 instance.
Re:AWS’s Anti-Competitive Move Hidden in Plain Sight by daneel_w on Saturday March 18, 2023 @02:10PM (#35211598)
Yes, which we're doing these days. It's how we ran into this "enterprise feature".
Re:AWS’s Anti-Competitive Move Hidden in Plain Sight by brycelarkin on Saturday March 18, 2023 @05:51PM (#35213447)
Some other things:

1. Depreciation of NAT instance ami in favor of managed NAT

2. No EKS free tier

Re:AWS’s Anti-Competitive Move Hidden in Plain Sight by roncesvalles on Saturday March 18, 2023 @06:33PM (#35213839)
How are these anti-competitive?
Re:AWS’s Anti-Competitive Move Hidden in Plain Sight by daneel_w on Sunday March 19, 2023 @04:20PM (#35223139)
Makes it harder for you to roll your own on EC2 for lower cost.
Re:AWS’s Anti-Competitive Move Hidden in Plain Sight by adave on Saturday March 18, 2023 @08:07PM (#35214532)
True but you can't blame them to add some friction to stuff that's a loss for them and make profit features more convenient. What's better is to know these things like you do and not use AWS is the above area deal breaker. Unfortunately they don't play nice since they can do that which is anti competitive but hey they'll give you 1st year free lol.
Re:AWS’s Anti-Competitive Move Hidden in Plain Sight by amluto on Saturday March 18, 2023 @09:29PM (#35215048)
> It's easy to set Aurora up as "slave" for accepting replication data from an external MariaDB/MySQL server

Huh. I tried setting up AWS RDS MySQL to replicate from an external MySQL awhile ago, and the experience was almost comically poor. Is Aurora better?

If you generate a mysqldump and have the command line options set to correctly store the binlog or the GTID data to allow replication to start in the right place, RDS chokes.

Re:AWS’s Anti-Competitive Move Hidden in Plain Sight by daneel_w on Sunday March 19, 2023 @04:19PM (#35223126)
>"Is Aurora better?"

This was back on Aurora 1 (based on MySQL 5.6), and setting it up as "slave" was identical to how one would go about it for regular MariaDB/MySQL.

Re:AWS’s Anti-Competitive Move Hidden in Plain Sight by birdyrooster on Saturday March 18, 2023 @11:17PM (#35215691)
OP was a better example than yours by a large margin.