NoSQL: Why it's So Damn Sticky
roadtofailure.com
NoSQL: Why it's So Damn Sticky
1–10 of 39 posts
Re: NoSQL: Why it's So Damn Sticky
#2Re: NoSQL: Why it's So Damn Sticky
#3Tapirs accounting for 78% of the world economic output? Pikachus in a blender? I think he's finally lost it.
Re: NoSQL: Why it's So Damn Sticky
#4Perfect.
Re: NoSQL: Why it's So Damn Sticky
#5Re: NoSQL: Why it's So Damn Sticky
#6Re: NoSQL: Why it's So Damn Sticky
#7Tapirs accounting for 78% of the world economic output? Pikachus in a blender? I think he's finally lost it.
Kept you reading for the whole thing though, didn't he?
Just to clarify: I don't mean to say that I didn't read the article. I mean to say that the tapir analogy was distracting and detracted from the article.
Re: NoSQL: Why it's So Damn Sticky
#8"Error establishing a database connection" Perfect.
Re: NoSQL: Why it's So Damn Sticky
#9You´d be wrong...
This essay is long and disorganized. To spare those who would other wise have to suffer through it the trouble: It's basically a defense of the the term 'NoSQL' as a description of the collective of hash-key stores, documents dbs, etc that have been gaining popularity of late. His claim: 'NoSQL' represents some kind of escape from the oppressiveness of SQL and is a radical break with accepted DB technologies.
It's posts like this that bother me most about about the NoSQL crowd. Hash-key stores, document DBs, and other equally innovative things have been in existence and in use for decades. Periodically, people try to promote these technologies as replacements for RDBMs and each time, we learn that while they have their place, so do RDBMs. NoSQL is not revolutionary; it's a practical extension of pre-existent technologies that solves a set of problems that current RDBMs don't address, while RDBMs still solve the set of problems that they were meant to address.
All this revolution nonsense is just that, and that's why people are so worked up on both sides.
Re: NoSQL: Why it's So Damn Sticky
#10All the people that show up to NoSQL articles and say, "you should always use SQL" are the ones that happened to use relational databases for the right tasks.
I wish there was a delay between when screws were invented and when screwdrivers were invented so that we could have seen the NoHammer movement. Of course you shouldn't screw in screws with a hammer. But hammers handle nails pretty well.