Stop calling me NoSQL
blog.dhananjaynene.com
Stop calling me NoSQL
1–10 of 21 posts
Re: Stop calling me NoSQL
#2How about this 4-letter acronym: NSQL (Native Storage Query Language)?
Re: Stop calling me NoSQL
#3We should be very happy that somebody invented the "NoSQL" name. Once things have a name people can start to talk about this things, and the ideas will move faster.
This recent hype about the NoSQL stuff was only possible because there was a name :)
Re: Stop calling me NoSQL
#4How about this 4-letter acronym: NSQL (Native Storage Query Language)?
I think this might be a misnomer in that NoSQL in the general sense describes a set of technologies acting as value stores rather than a standardized language for accessing said values.
Re: Stop calling me NoSQL
#5How about this 4-letter acronym: NSQL (Native Storage Query Language)?
I think this might be a misnomer in that NoSQL in the general sense describes a set of technologies acting as value stores rather than a standardized language for accessing said values.
Native storage query language implies using native i.e., non-standardized query language and API. It's an categorical acronym like AJAX.
Re: Stop calling me NoSQL
#6We should be very happy that somebody invented the "NoSQL" name. Once things have a name people can start to talk about this things, and the ideas will move faster. This recent hype about the NoSQL stuff was only possible because there was a name :)
[deleted]
Re: Stop calling me NoSQL
#7We should be very happy that somebody invented the "NoSQL" name. Once things have a name people can start to talk about this things, and the ideas will move faster. This recent hype about the NoSQL stuff was only possible because there was a name :)
This reminds me of when the term AJAX was introduced. I thought it was a stupid attempt to foist a "cool" name on an already existing term.
Yet it may be coincidental but that seemed to coincide with the time that using an XMLHTTPRequest took off.
Maybe the branding worked?
Re: Stop calling me NoSQL
#8We should be very happy that somebody invented the "NoSQL" name. Once things have a name people can start to talk about this things, and the ideas will move faster. This recent hype about the NoSQL stuff was only possible because there was a name :)
The NoSQL hype happened because people wanted to explore and promote alternatives. The NoSQL name happened since there was a need to provide a moniker to the alternatives. Since this was a hype and movement based on otherwise real need, it is likely to have happened even if the name was something completely different say FreeQL (or whatever other catchy name). The post isn't arguing there shouldn't be a name. All it is attempting to point out is that it should be a meaningful and appropriate name - else what you think (when you hear the name) and what you get (when you actually dig into the details) are very different. The current name actually makes it harder for newer participants to properly grok these storage systems - which wasn't perhaps the goal in the first place.
Re: Stop calling me NoSQL
#9How about this 4-letter acronym: NSQL (Native Storage Query Language)?
I like the name posted by someone in the comments -- NoTable.
Re: Stop calling me NoSQL
#10it seems like you’re looking for realistically structured data, not data twisted to fit a formula convenient for mathematicians.
The appropriate words here are "logical" and "physical" not "real" and "unreal". A relation is a logical data structure. Hash tables, trees, and graphs are all physical data structures.
Another accurate thing to say is that hash tables, trees and graphs are all "pointer-based databases" and relational databases are "pointer-free databases".
The second one will be confusing to people accustomed to putting pointers into relations (like what rails does) and turning the relational database into an ad-hoc graph database.