I Can't Wait for NoSQL to Die
teddziuba.com
I Can't Wait for NoSQL to Die
1–10 of 80 posts
Re: I Can't Wait for NoSQL to Die
#2As is to be expected from this author, this is definitely on the flame-bait side of things. I submit it because I believe there is an important point here: for the vast majority of startups, going with a relatively unproven "NoSQL" database is a premature optimization and an unneeded technical risk. I disagree with the author that these databases are a flash in the pan, but their over-application is.
Re: I Can't Wait for NoSQL to Die
#3The author makes some very valid points, but I will retort that RDBMS are overused as well.
Sometimes you just want to store data on the disk in a safe and language agnostic way.
You don't care about relations.
In that case, many "NoSQL" engines are really great.
Re: I Can't Wait for NoSQL to Die
#4+1 for the Batman rollerblader. But that's about it. Use what works, some apps do justify nosql off the bat. Many don't.
Re: I Can't Wait for NoSQL to Die
#5The author makes some very valid points, but I will retort that RDBMS are overused as well. Sometimes you just want to store data on the disk in a safe and language agnostic way. You don't care about relations. In that case, many "NoSQL" engines are really great.
"Sometimes you just want to store data on the disk in a safe and language agnostic way."
You mean, kind of like a file?
Re: I Can't Wait for NoSQL to Die
#6NoSQL will never die, but it will eventually get marginalized, like how Rails was marginalized by NoSQL.
Is it just me, or does this statement make absolutely no sense whatsoever?
Re: I Can't Wait for NoSQL to Die
#7Ted's point may be valid for BigTable-like databases. (I'm not saying it is, but I don't know enough about those to say so.) Those are designed for scalability and if you don't need the scalability you probably should use a RDBMS instead.
But there are other advantages of SQL-less databases that don't deal with scale. I deployed my first MongoDB app a couple weeks ago. Even though it was a small (~1 developer month) project, and neither myself nor the other developer had used MongoDB before, I still think we finished faster than if we'd used MySQL. Just like Cassandra is a premature optimization if you just need an RDBMS, an RDBMS is a premature optimization if you only need an object store.
Re: I Can't Wait for NoSQL to Die
#8The author makes some very valid points, but I will retort that RDBMS are overused as well. Sometimes you just want to store data on the disk in a safe and language agnostic way. You don't care about relations. In that case, many "NoSQL" engines are really great.
"Sometimes you just want to store data on the disk in a safe and language agnostic way." You mean, kind of like a file?
Well, since you need a safe way, you'll need a locking mechanism, too. And since it needs to be language agnostic, you can't just dump the internal representation of your object to disk, so you need some sort of serialization.
At that point, it's probably easier to go with an already existent object or document store.
Re: I Can't Wait for NoSQL to Die
#9As is to be expected from this author, this is definitely on the flame-bait side of things. I submit it because I believe there is an important point here: for the vast majority of startups, going with a relatively unproven "NoSQL" database is a premature optimization and an unneeded technical risk. I disagree with the author that these databases are a flash in the pan, but their over-application is.
I dunno, I see the opposite: RDBMS's are a premature optimization. In my experience, it's /much/ easier to hack together a quick webapp in MongoDB, because you don't have to worry about relations, migrating schema, etc. Sure, it might be slower than Postgres on a billion-row table, but wait until you have a million rows before you shackle yourself to the relational constraints.
Re: I Can't Wait for NoSQL to Die
#10Ted's point may be valid for BigTable-like databases. (I'm not saying it is, but I don't know enough about those to say so.) Those are designed for scalability and if you don't need the scalability you probably should use a RDBMS instead. But there are other advantages of SQL-less databases that don't deal with scale. I deployed my first MongoDB app a couple weeks ago. Even though it was a small (~1 developer month)…
I got downvoted awfully last night for trying to say this, but I'll say it again to back you up:
Developing with mongodb is _lightning fast_ and holds up very very well. If you end up with problems, switch to SQL later!
I don't think a lot of these people hating on the nosql projects have actually tried building something with them.