A Year of MongoDB
speakerdeck.com
A Year of MongoDB
1–10 of 133 posts
Re: A Year of MongoDB
#2Slide 56 states: "Schema vs. Schema-less is just a different version of dynamic typing vs. static typing."
Wrong.
If anything, it is a different version of weak typing vs. strong typing. That is totally orthogonal.
Re: A Year of MongoDB
#3I can confirm that the map-reduce thing does not hold up to any performance-wise expectations.
Re: A Year of MongoDB
#4I can confirm that the map-reduce thing does not hold up to any performance-wise expectations.
I assume your experience was on version Now that 2.4 is out I'm interested in seeing how much the switch to multithreaded V8 has improved that. http://docs.mongodb.org/manual/release-notes/2.4-javascript/
Re: A Year of MongoDB
#5I just submitted a related article on Hyperdex which, although it's not Python, has a very good Python interface.
Re: A Year of MongoDB
#6Why the URL are not working from the SpeakerDeck document? Captain Obvious here: But isn't that the purpose of the Web? It's the WEB... make those links work!
Re: A Year of MongoDB
#7I'm a little blown away by the total lack of technical understanding when it comes to MongoDB. This person is obviously very technical, so why would he have chosen MongoDB in the first place? It isn't like MongoDb's technical shortcomings are a secret. The description of how MongoDb does sharding and distributed queries should have immediately raised red flags to any who has even a modicum of CAP understanding. If it sounds complex, a total hack and impossible to manage it probably is.
For gosh sakes, even the 10gen guys admit MongoDB lost data a year(!) ago. [1] If a database lost data in a single server configuration, why would you trust it as a cluster?
Re: A Year of MongoDB
#8I'm a little blown away by the total lack of technical understanding when it comes to MongoDB. This person is obviously very technical, so why would he have chosen MongoDB in the first place? It isn't like MongoDb's technical shortcomings are a secret. The description of how MongoDb does sharding and distributed queries should have immediately raised red flags to any who has even a modicum of CAP understanding. If it…
Sometimes the decision of what technology to use and the task of making it work for your needs are entirely disconnected.
Re: A Year of MongoDB
#9Who is still surprised by this? I feel that after 2-3 years of the litany of stories and cases like this, it should shock absolutely no one anymore.
Re: A Year of MongoDB
#10I'm a little blown away by the total lack of technical understanding when it comes to MongoDB. This person is obviously very technical, so why would he have chosen MongoDB in the first place? It isn't like MongoDb's technical shortcomings are a secret. The description of how MongoDb does sharding and distributed queries should have immediately raised red flags to any who has even a modicum of CAP understanding. If it…
I was more surprised by a technical post complaining about workers, waiting on io, and context switching. There are ways to handle concurrency and network communication without large amounts of context switching and threads.