3 ms·
That's because NoSQL was never meant to be a "movement". We were taking a trip to the Bay Area from London and we wanted to meet up with some of the guys who we
by russss 17y ago
That's because NoSQL was never meant to be a "movement". We were taking a trip to the Bay Area from London and we wanted to meet up with some of the guys who were working on scalable non-relational data stores. We planned a one-day conference and someone suggested naming it NoSQL.
It was just a tongue-in-cheek name, until someone came along and decided it was a "movement".
- geebee 17y agoThat makes sense, sounds like it got away from you (kind of like "agile", which has lost a lot of its original meaning). But there's a reason it got away from you, and that "NoSql" struck a broader chord. There are a lot of reasons people would say "no sql". Some of them are good, some of them are ill-considered, and some are probably just a matter of personal preference. I personally like sql and relational algebra, but that doesn't mean I enjoy writing a lot of dull sql for crud apps, so even a SQL fanboy like me does see some merit to a more general "no sql" movement. I'm just interested in trying to figure out/catalog the various objections, why people have them, whether they are based on a misunderstanding of SQL/RDBMS or are very valid, and so forth. I think it's a good discussion.