Earlier quoted context omitted.
What's the hot shit right now then, if not Node?
Meteor, websocket-dbs.
Goodbye, MongoDB
111–120 of 123 posts
Re: Goodbye, MongoDB
#112Re: Goodbye, MongoDB
#113Earlier quoted context omitted.
Ah. If your target is people who aren't going to be reading docs, I don't think any DB is really preferable. :) Any more details about the project, or is it under wraps?
It's basically a simple blogging platform, going to be released OSS. Most devs know how to get MySQL running without too much thought, but many don't even know what Postgres is.
If it's only a simple blogging platform, it might well be that MySQL will do the job just fine though.
Re: Goodbye, MongoDB
#114Wow, how many "Goodbye, MongoDB" stories are coming? The last days had several ones. Not sure if this is already a trend?
IIRC We've had several "Goodbye CouchDB" articles in the past few weeks too. What's the under/over on the inevitable "Goodbye Riak" wave?
Riak's relative obscurity actually serves well in this regard. Odds are that if you discover Riak, you do so for a reason - you've been searching, you have a specific itch that needs to be scratched, etc. Given that you are already pretty clued when you get to it, you are extremely unlikely to pick it for the wrong reason, and consequently the success rate tends to be astonishingly high. Mind you, I'll add that the folks at Basho are some of the nicest people I know, and that helps a lot :-)
Bottom line - I really don't expect Riak to go away anytime soon...
Re: Goodbye, MongoDB
#115Re: Goodbye, MongoDB
#116While some of the author's criticisms are valid, some of them are completely wrong: > Having no option to perform an operation comparable to UPDATE table SET foo=bar WHERE.... What? db.collection.update does exactly this. See: http://www.mongodb.org/display/DOCS/Updating#Updating-update... MongoDB fit a nice niche for a read heavy mid-scalability db solution. Every DB has it's niche. Trying to use it outside of what…
Yes, moving your data from Mongo to PgSql, MySql, MSSql, Oracle, etc. is going to be difficult.
However: why start with a production level Oracle install anticipating "web scale" when you're not going to have more than ~1k users at launch.
People look to Google and Twitter and Facebook for advice on how to scale. They then apply this advice far before they need to.
I don't think you should plan to be large scale from the get-go. I think you should have a plan for what you're going to do if you get big.
My $.02
Re: Goodbye, MongoDB
#117Hell yeah. From what I've seen of MongoDB I'm not impressed at all. In some carefully controlled cases, performance would be acceptable, but change anything at all (even the order that data is inserted) and it just sucks. For one particular application, the performance difference between MySQL and Mongo was like the difference between the Space Shuttle and a Chevy Sonic.
I think it's important people understand WHY this is the case, because it's not simply an issue for MySQL vs Mongo. The simplest way to get really good performance for multi-row queries (even if you fall out of cache) is to physically order your data in query-order. (that is, if you are going to ask for the most recent 100 blog comments, order the comments by (blog-post-id, reverse comment-date). MySQL -Innodb makes…
Big advantage in that option (Postgres, MSSQL, Oracle).
Re: Goodbye, MongoDB
#118is there any replacement for mongodb?
Re: Goodbye, MongoDB
#119Re: Goodbye, MongoDB
#120My Xen VM crashed several times by day during several weeks. And, this problem disappears when I removed my mongodb database...