Oh look, another "We thought Mongo was a silver bullet and found out that was wrong" post.
Why MongoDB Never Worked Out at Etsy
11–20 of 73 posts
Re: Why MongoDB Never Worked Out at Etsy
#12Whenever I see articles come up like this one mentioning MongoDB, I wonder not why people decided to go with Mongo, but why they didn't go with some of the alternatives out there? For my part, we use Couchbase to great success and it fixes many of the complaints against MongoDB. Then there's Riak and countless others with well established quality installations. To me MongoDB seems the buzzword NoSQL engine that gets used for 'play' projects, but not much in the way of real-world implementations. Thoughts?
Re: Why MongoDB Never Worked Out at Etsy
#13Most of the production deployments I find on the internet are around 3-5 nodes. Are there any production clusters that are running 500-600+ nodes?
Re: Why MongoDB Never Worked Out at Etsy
#14Whenever I see articles come up like this one mentioning MongoDB, I wonder not why people decided to go with Mongo, but why they didn't go with some of the alternatives out there? For my part, we use Couchbase to great success and it fixes many of the complaints against MongoDB. Then there's Riak and countless others with well established quality installations. To me MongoDB seems the buzzword NoSQL engine that gets…
Did you read the article? His main reason had nothing to do with Mongo itself.
Re: Why MongoDB Never Worked Out at Etsy
#15Whenever I see articles come up like this one mentioning MongoDB, I wonder not why people decided to go with Mongo, but why they didn't go with some of the alternatives out there? For my part, we use Couchbase to great success and it fixes many of the complaints against MongoDB. Then there's Riak and countless others with well established quality installations. To me MongoDB seems the buzzword NoSQL engine that gets…
Did you read the article? His main reason had nothing to do with Mongo itself.
Yes, yes I did. My question is why it was selected in the first place, rather than a period of exploration of the benefits and drawbacks of the different NoSQL solutions (which perhaps might have stopped this particular test-case from being a failure). The article doesn't mention those details though.
Also, we DO implement a two DB setup... Couchbase and MySQL. They both have their place.
Re: Why MongoDB Never Worked Out at Etsy
#16[deleted]
Re: Why MongoDB Never Worked Out at Etsy
#17Genuine question- who is using MongoDB successfully in production, and at scale? I'm not aware of anyone myself- I hear of it being used in hackathons etc because its so quick to set up, but I'd be curious to know what people are using it with.
I'm using it for the analytics suite at my company (large ecommerce multinational).
Its weird at first, coming from a background of Access then SQLite then MySQL/PHPMyAdmin but you get used to it. I essentially treat it like a gigantic python dictionary object.
The sharding is too much of a ball-ache to set up so I've created an optimal way of distributing/mapping files across our cluster to make use of all machines.
Data integration is nice. Making sure there's no temptation to output each integrated line to the terminal, pymongo and its C extensions can integrate a ~500 byte record in ~0.0001 seconds.
Basically the main advantage is not having a schema whatsoever - you can just add random attributes to documents whenever the hell you want. But later you have to be careful with exception handling since documents might not have the attributes you expect.
Re: Why MongoDB Never Worked Out at Etsy
#18Earlier quoted context omitted.
Did you read the article? His main reason had nothing to do with Mongo itself.
Yes, yes I did. My question is why it was selected in the first place, rather than a period of exploration of the benefits and drawbacks of the different NoSQL solutions (which perhaps might have stopped this particular test-case from being a failure). The article doesn't mention those details though. Also, we DO implement a two DB setup... Couchbase and MySQL. They both have their place.
I don't think you read it very carefully; the second sentence links to the earlier article where they list the reasons they chose that tech over others.
> I wrote about what I was thinking at the time here [1]
Re: Why MongoDB Never Worked Out at Etsy
#19Whenever I see articles come up like this one mentioning MongoDB, I wonder not why people decided to go with Mongo, but why they didn't go with some of the alternatives out there? For my part, we use Couchbase to great success and it fixes many of the complaints against MongoDB. Then there's Riak and countless others with well established quality installations. To me MongoDB seems the buzzword NoSQL engine that gets…
You can't currently change only a single field in couchbase (ex:increment this field) in neither couchbase nor riak.
Range sharding (for saas,shard by client_id).
No sorting by value on couchbase indexes? And many other small features.
On the other hand i love about couchbase: no mongos,all servers equal.
Re: Why MongoDB Never Worked Out at Etsy
#20Genuine question- who is using MongoDB successfully in production, and at scale? I'm not aware of anyone myself- I hear of it being used in hackathons etc because its so quick to set up, but I'd be curious to know what people are using it with.
Gaug.es uses Mongo. Its data model is pretty simple (just counters), but he has blogged about the approach in detail.
MongoDB Counters: http://railstips.org/blog/archives/2011/06/28/counters-every... http://railstips.org/blog/archives/2011/07/31/counters-every...
Kestrel: http://railstips.org/blog/archives/2012/03/05/misleading-tit...
Gets some decent traffic and works well.