291–297 of 297 posts
Earlier quoted context omitted.
> You have to read all of that pretty carefully to understand that it's NOT MongoDB I disagree. If I see "Blah-compatible" I know it's not blah.
Really? Because AWS Aurora is "MySQL compatible" but I assume they did not build it from the ground up. It's surely a MySQL fork.
Earlier quoted context omitted.
Morally it might be questionable, if it puts MongoDB out of business and reinforces the AWS "monopoly". However, MongoDB selected a free and open source license. This was always in the cards. They went with AGPL to keep the source maximally open for end users, but that never protected their revenue stream. (Some JS SDK companies used it for that purpose, where it makes some sene, but a DB is very different.) But if t…
They recently switched to a new license, inspired by AGPL, that isn’t approved by OSI and probably not Open Source. So they are trying to eat their cake and have it too.
I sort of agree with their sentiment, but of course they are late to the have-cake-will-have-it-and-eaten-it-too party, as now AWS was able to fork the last AGPL-ed version and be done with it.
Earlier quoted context omitted.
Morally it might be questionable, if it puts MongoDB out of business and reinforces the AWS "monopoly". However, MongoDB selected a free and open source license. This was always in the cards. They went with AGPL to keep the source maximally open for end users, but that never protected their revenue stream. (Some JS SDK companies used it for that purpose, where it makes some sene, but a DB is very different.) But if t…
I doubt AWS wants Mongo out of business or else who do they have to migrate into and all they will have left is yet another NoSQL now only used in AWS.
Even if MongoDB goes out of business, or becomes less popular AWS benefits as they can keep selling to these "legacy" customers their super-stable AWSgoDB, and said customers will just eat it all up without thinking.
Earlier quoted context omitted.
Any company bets on Amazon not being able to rewrite their software loses the bet. They even have their own CPUs because one of the CPU vendors failed to meet with their demands.
Disclosure: I'm part of the EC2 team at AWS We launched A1 instances with our Arm-Based AWS Graviton Processors to increase the selection of technology for our customers. It has nothing to do with demands of vendors, and everything to do with increasing choice, providing access to extensive technology ecosystems like those Arm has been building with their partners, and lowering costs.
Amazon was using MongoDB without paying for it. MongoDB found that objectionable, and changed the license such that Amazon would either have to pay, or stop using it. Amazon stopped using it, and started using its own in-house implementation instead (presumably because it was cheaper to develop it than to pay MongoDB). So, MongoDB got exactly what they asked for. It's just that, when they forced Amazon to make a choi…
Amazon was never using Mongo. They used Dynamo, and their white paper on it predates Mongo. Amazon was always an Oracle shop and now have dropped that too. My old company begged AWS for years for Mongo, looks like they finally got around to it.
Self hosting MongoDB has always been a pain if you only have a small amount of data in it. The scaling goes one host, master/slave (which existed, though people would argue with you that it didn't), to 7+ separate hosts if you're going to build it properly (2x mongoose with DNS across them, 3x config cluster, 3x data cluster).
That's a hell of a jump for someone only using Mongo incidentally. You can cheat and combine multiple pieces of the cluster on single hosts but if that fails you can then get into weird multi-component failure issues.
Earlier quoted context omitted.
For what it's worth when it comes to choosing a hosted ElasticSearch provider I would go to Elastic over AWS Elasticsearch Service.
Interesting, as someone considering using AWS ES for an upcoming project I'd love to hear more about your experience.
Earlier quoted context omitted.
Who decides what's the conflict of the interest. Developers?
Ultimately, if there's a disagreement over this, it would be the courts, since it's in the employment contract.
However, if that is the case, I’d love to know how so one can implement similar processes internally!