21–30 of 66 posts
Earlier quoted context omitted.
Can you elaborate on this? What's wrong with MongoDB?
This. http://hackingdistributed.com/2013/01/29/mongo-ft/ Also this. http://nyeggen.com/blog/2013/10/18/the-genius-and-folly-of-m...
https://blog.serverdensity.com/tech-behind-time-series-graph...
This is nothing wrong with MongoDB.
I find it somewhat depressing that the first comments on any post about MongoDB generally seem to be short, disparaging and dismissive without offering much if any substance. We use MongoDB in production, processing millions of new records every month and it works great. Our data has differing and evolving schemas and can be used as JavaScript objects or python dictionaries with little effort. It works and performs w…
There was a spate of high profile "why we moved from MongoDB to $other_database" articles a year or so ago of startups getting burned when they realised that the all-signing all-dancing cure-all database they (thought they) had been sold, in fact wasn't. The issues encountered ranged from MongoDB failing to scale out as easily as promised, to significant loss of data. There was also some backlash because MongoDB didn…
This is probably what raised awareness of the issues of MongoDB http://www.slideshare.net/emiltamas/scaling-with-mongo-db-wi... and it's from 2011
It's a lot of time for a software project
I find it somewhat depressing that the first comments on any post about MongoDB generally seem to be short, disparaging and dismissive without offering much if any substance. We use MongoDB in production, processing millions of new records every month and it works great. Our data has differing and evolving schemas and can be used as JavaScript objects or python dictionaries with little effort. It works and performs w…
> It works and performs well for us and our use case. 100% agree. I think it's become cool to knock MongoDB, just because it is MongoDB. It isn't a silver bullet, and its use cases are more limited than RDBMs. But if you know what you're doing, it has some great applications.
* Do you have a customer yet? If not, technology choices do not matter, go build your product as fast as possible and get a customer.
* Is your system starting to have slow performance during max usage? If so, every system will have a few easy optimizations, find those using something like NewRelic. Aside from those, technology choices do not matter, throw money at any scaling problem (at this point, it typically isn't that much money). This will optimize your time for sales and marketing to get more customers.
* Is your system starting to buckle under the weight of customers? If so, go hire someone who can scale everything you learned from your customers, and not someone who bends to the latest trends on HN.
Here is an article on my philosophy and experience with scaling businesses and architectures: http://blog.mongohq.com/changing-the-growth-formula/
I find it somewhat depressing that the first comments on any post about MongoDB generally seem to be short, disparaging and dismissive without offering much if any substance. We use MongoDB in production, processing millions of new records every month and it works great. Our data has differing and evolving schemas and can be used as JavaScript objects or python dictionaries with little effort. It works and performs w…
There was a spate of high profile "why we moved from MongoDB to $other_database" articles a year or so ago of startups getting burned when they realised that the all-signing all-dancing cure-all database they (thought they) had been sold, in fact wasn't. The issues encountered ranged from MongoDB failing to scale out as easily as promised, to significant loss of data. There was also some backlash because MongoDB didn…
Earlier quoted context omitted.
This. http://hackingdistributed.com/2013/01/29/mongo-ft/ Also this. http://nyeggen.com/blog/2013/10/18/the-genius-and-folly-of-m...
Because some people don't use it correctly doesn't mean it can't be done. Here is a different random article about ServerDensity using it successfully https://blog.serverdensity.com/tech-behind-time-series-graph... This is nothing wrong with MongoDB.
Earlier quoted context omitted.
There was a spate of high profile "why we moved from MongoDB to $other_database" articles a year or so ago of startups getting burned when they realised that the all-signing all-dancing cure-all database they (thought they) had been sold, in fact wasn't. The issues encountered ranged from MongoDB failing to scale out as easily as promised, to significant loss of data. There was also some backlash because MongoDB didn…
Do you think it is MongoDB problem or all NoSQL dbs has the some problem?
Once a DBMS like MongoDB gets popular, then people uncover some of its failings and write about them...which is great because it means you don't have to discover the same things the hard way. But it's a drag too because there's no database system that everyone agrees is adequate (much less ideal) for every application.
Here's my one-word guide: Don't.
I find it somewhat depressing that the first comments on any post about MongoDB generally seem to be short, disparaging and dismissive without offering much if any substance. We use MongoDB in production, processing millions of new records every month and it works great. Our data has differing and evolving schemas and can be used as JavaScript objects or python dictionaries with little effort. It works and performs w…
It's because mongodb just isn't as good at queries as a relational db, while also not offering the scalability benefits that other nosql databases do. Also the attitude that mongodb takes towards data - namely, convenience and performance first, data safety second - is very incompatible with most uses for a database.