So there’s a bit of a swelling around the idea of NoSQL. That is, databases that don’t have an SQL interface in front of them – with the promise of better performance. With a well designed backend, this is no doubt the case.
A flexible query language is rather useful though. I think we’ll see the rise of AlsoSQL. That is systems that present a fast and simple protocol along with a SQL interface.
This hybrid system has seen use for many years. MySQL Cluster is one such example. SQL through MySQL Server, NoSQL through NDB API.
With Drizzle, I feel we’ll be in a pretty good position to offer non-sql based protocols and access methods to existing storage engines.
I like the title :)
But I believe it will be more like SomewhatSQL. That is, the SQL interface will be simplified (not for Drizzle — for the other NoSQL solutions). Somewhat like sphinx’s ability to parse SQL.
Not sure I understand all the NoSQL excitement. Isn’t this exactly what Sleepycats BDB engine did years ago?
I believe too, current databases have a complicated SQL interface, and Drizzle could have a shot at that.
Microkernel architecture and plugin interface will help Drizzle provide NoSQL interface as well.
Stewart,
Completely agree that we need flexible, expressive query languages. And I think SQL does not always fit the bill…
I replied to your post on the drizzle discuss list, here is the link:
https://lists.launchpad.net/drizzle-discuss/msg06431.html
You don’t even need to use NDB to get NoSQL with MySQL – use the HANDLER statement.. ;)
Although HANDLER is just a bit scary :)
So are many NoSQL implementations :P
That is very true too :)
@Stewart: checked out MQL yet?
With the 7.1 release of MySQL Cluster, we will also have a Java wrapper and OpenJPA plug-in to take much of the complexity out of direct NDB api access, without any significant compromise in performance
Hi Stewart,
Is AlsoSQL a common term? While I believe that people will come back to SQL world after hanging around NoSQL, as its efficiency and usefulness might be really competitive when people have to develop web service so rapidly, I’ve been wondering how I should call “Not Only NoSQL” such as YesSQL, which is funny but an impressive phrase :)
If AlsoSQL is a common term, I’ll use it, but it’s not so common, I’d love to dig into other possibilities.
Kind regards,
—
Mikiya
I just made it up – no idea if anybody else has used AlsoSQL (but from a quick Google, it looks like nobody has).
I also like YesSQL though…. although it is more non-NoSQL. I like AlsoSQL as it is rather inclusive.
How about AgainSQL, KnewSQL, sounds like ‘new’, MoreSQL, GoSQL, BaSQL – Born Again SQL, YwcSQL – Yes we can SQL? ;)
Check out “post-relational” databases…
use as key/value, hierarchical, object, relational, or multivalue…
InterSystem’s Caché does all that, with the speed of an in-memory database.