I don't understand why people are reacting to it so aggressively. That's basically how AWS works, they did the same to Apach Kafka with Kinesis, Prestodb with Athena, PostgreSQL and MySQL with Aurora, Redis with ElastiCache and many others over the last 4 years so it's not new. It took too long for the open-source community to figure out that the cloud providers are killing them, now it's too late. Well played, AWS.
Amazon DocumentDB, with MongoDB compatibility
231–240 of 323 posts
Re: Amazon DocumentDB, with MongoDB compatibility
#232I don't understand why people are reacting to it so aggressively. That's basically how AWS works, they did the same to Apach Kafka with Kinesis, Prestodb with Athena, PostgreSQL and MySQL with Aurora, Redis with ElastiCache and many others over the last 4 years so it's not new. It took too long for the open-source community to figure out that the cloud providers are killing them, now it's too late. Well played, AWS.
Re: Amazon DocumentDB, with MongoDB compatibility
#233Re: Amazon DocumentDB, with MongoDB compatibility
#234Now I kinda hope Oracle decides to buy out MongoDB and integrate it into their own cloud. Then Oracle can decide to pull the same bullshit that they did with Google over the Java APIs with the MongoDB APIs but now against their current enemy Amazon (and Microsoft, too). Then a combined Google + Amazon + Microsoft may finally be able to reverse the API Copyright insanity that is hovering ominously over the tech indust…
AWS is preemptively defensive about API licensing claims: "Amazon DocumentDB implements the Apache 2.0 open source MongoDB 3.6 API".
Re: Amazon DocumentDB, with MongoDB compatibility
#235I don't understand why people are reacting to it so aggressively. That's basically how AWS works, they did the same to Apach Kafka with Kinesis, Prestodb with Athena, PostgreSQL and MySQL with Aurora, Redis with ElastiCache and many others over the last 4 years so it's not new. It took too long for the open-source community to figure out that the cloud providers are killing them, now it's too late. Well played, AWS.
Well, people are angry about that, that’s why they react aggressively.
I think that it's too late considering AWS already did that to most of the industries but here is Hazelcast's take: https://www.linkedin.com/pulse/open-source-needs-protect-its...
Re: Amazon DocumentDB, with MongoDB compatibility
#236And if you are curious, no I don't have any special need or use case for it, just wondering.
Re: Amazon DocumentDB, with MongoDB compatibility
#237Earlier quoted context omitted.
Definitely because it was faster. Amazon's strategy is to launch new features ASAP and then rely on everyone having to be on-call to fix shit when it inevitably breaks in prod because they rushed to launch. I will admit that while their "operational excellence" is shit, the security engineers do have quite a bit of power to block launches so their security isn't as bad as the reliability. However, the fact that write…
AWS prioritizes launch above EVERYTHING. It is their strategy, to have market tells them what to build. I think it works, and AWS has yet been brought down by this horizontal complexity. Quite an achievement, but might not be a satisfying experience for the engineers work there.
I wonder how widespread this view is. I suspect it's more widespread than Amazon realise. They may have optimised into a local maximum where they get a lot of value from being first to market, but could potentially get more by being first to "viable to trust a business on".
Re: Amazon DocumentDB, with MongoDB compatibility
#238Earlier quoted context omitted.
What is the way out? Would love to hear from people.
Ultimately, Cantrill put it well: > ...for those open source companies that still harbor magical beliefs, let me put this to you as directly as possible: cloud services providers are emphatically not going to license your proprietary software. I mean, you knew that, right? MongoDB Inc cannot make Amazon pay commercial license fees. That is not a thing that will happen. They have a lever in front of them with two posi…
Was that even the goal? My impression of the licensing change was not that they expected to Amazon to pay fees for offering a hosted MongoDB service. It was instead to lock Amazon out, and keep MongoDB Inc. as the only "cloud provider" of a hosted MongoDB service (perhaps still on top of AWS but with separate management interface).
Re: Amazon DocumentDB, with MongoDB compatibility
#239If I'm reading the pricing page correctly, DocumentDB would run a _minimum_ of $200/month. That's for the smallest instance and no storage or I/O. Kind of steep if you ask me.
Besides that AWS will charge per transaction (at 0.2 per million) outrageous given that you already pay per instance. Correct pricing strategy needs to be per request or per instance, AWS is charging for both
I think the idea is that by charging precisely where they incur costs, they can be much more reactive to different usage patterns, and therefore be more competitively priced overall.
Although it certainly does create lock-in due to not being able to figure out your billing and accurately model alternatives.
Re: Amazon DocumentDB, with MongoDB compatibility
#240Earlier quoted context omitted.
Interesting, how long ago was that? I would be curious to know if the WiredTiger switch ever happened, and what that support relationship looks like not given the contentious relationship between MongoDB and AWS. The old Wired Tiger Inc website[1] still lists AWS as a customer. Then again, the relationship between AWS and Oracle is even more contentious and Aurora MySQL is one of AWS's most popular products so I don'…
3+ years ago, so it's entirely possible that things have changed since I left. I don't have any more recent information on the state of the system. At least when I was there, the strong focus was always on adding new features (global & local secondary indexes, change streams, cross-region replication, and so on) to keep up with the Joneses (MongoDB et al). Meanwhile, a bunch of internal Amazon teams were taking a dep…