Looks good. I used to use both MongoDB and CouchDB (for very different use cases) a lot but haven’t touched them in a long while.
Out of curiosity, what use cases did you have for CouchDB that weren't feasible with MongoDB?
Amazon DocumentDB, with MongoDB compatibility
11–20 of 323 posts
Re: Amazon DocumentDB, with MongoDB compatibility
#12AWS lacked something like this before, which is why I used MongoDB Atlas (MongoDB's own managed mongo service). How is this different than DynamoDB (other than the obvious API differences)?
DynamoDB has specific requirements on how data is partitioned. You have to do upfront planning on how you access your data based on keys.
Mongodb is more flexible in this regard.
I’m sure there’s other big differences but this is the biggest to my experience with both.
Re: Amazon DocumentDB, with MongoDB compatibility
#13Finally an AWS service where the name makes sense and describes what it is. I hope this is the start of a trend.
I love Azure for this. The names are almost all extremely straightforward. There are a handful that have made the jump from confusing to straight forward, and a handful that have made the jump from straightforward to confusing (CosmosDB, formerly DocumentDB, chiefly comes to mind).
Agreed. Too bad the Azure portal is the polar opposite. AWS, for all its faults, is mostly just a boring HTML portal but it works.
Azure tried to get fancy, with side sliding panels all over the place, and it is barely useable. The nicest thing I can say is it is "quirky." It isn't really productive however, particularly not on my 1080p monitor at Windows 10's default 125% DPI.
I literally quit Azure's Application Insights and went back to Google Analytics simply because I hated the Azure UI with a burning passion of a thousand suns.
The concept of writing queries is good, but if that's the only way you can get at your data you better make it damn easy, and they didn't. I'm sure for full time data pros it is a dream however.
Re: Amazon DocumentDB, with MongoDB compatibility
#14Serious question: is there any real reason to use Mongo over Elasticsearch?
Re: Amazon DocumentDB, with MongoDB compatibility
#15Finally an AWS service where the name makes sense and describes what it is. I hope this is the start of a trend.
Surprised they didn't go with a 3-letter acronym. AWS DDB.
Recently I made a typo on a formal document. Wrote "AMI" when I meant to to write "IAM". Oops.
Re: Amazon DocumentDB, with MongoDB compatibility
#16seems an obvious response to https://www.mongodb.com/press/mongodb-issues-new-server-side...
I think it is likely it was the other way around. MongoDB caught wind of what AWS was about to release and changed the license.
Re: Amazon DocumentDB, with MongoDB compatibility
#17Serious question: is there any real reason to use Mongo over Elasticsearch?
I run a startup that uses both of these.
Mongo is a heck of a lot easier to configure and develop with, and works great as a general database with a rapidly changing schema.
Elasticsearch is great at solving specific problems like searching for items in a specific way, but it's got quite a learning curve and is pretty painful to host and configure compared to Mongo where you can have a prod instance going in seconds.
Re: Amazon DocumentDB, with MongoDB compatibility
#18If 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.
Re: Amazon DocumentDB, with MongoDB compatibility
#19Finally an AWS service where the name makes sense and describes what it is. I hope this is the start of a trend.
Surprised they didn't go with a 3-letter acronym. AWS DDB. Recently I made a typo on a formal document. Wrote "AMI" when I meant to to write "IAM". Oops.
DDB is typically used to denote DynamoDB
Re: Amazon DocumentDB, with MongoDB compatibility
#20AWS lacked something like this before, which is why I used MongoDB Atlas (MongoDB's own managed mongo service). How is this different than DynamoDB (other than the obvious API differences)?
DynamoDB has specific requirements on how data is partitioned. You have to do upfront planning on how you access your data based on keys. Mongodb is more flexible in this regard. I’m sure there’s other big differences but this is the biggest to my experience with both.
I was asking about DocumentDB, not MongoDB, but maybe I missed something. From their site:
> Amazon DocumentDB implements the Apache 2.0 open source MongoDB 3.6 API by emulating the responses that a MongoDB client expects from a MongoDB server, allowing you to use your existing MongoDB drivers and tools with Amazon DocumentDB
So, is this a "managed MongoDB" or is it a NOSQL AmazonDB that just implements the same API as MongoDB? If the latter, I don't think we can assume this is the same thing as MongoDB, because the internals might be completely different.