Cloud Zone is brought to you in partnership with:

I am still a big nerd in a (not so) small body. A technology freak with years of experience on anything from PL1/mainframe to LAMP. I love to code and talk about coding, especially on state of the art technologies - but only those that make some sense. My specialty is taking good technology and turning it to a cool product. I've done this in my previous roles, and I'm doing it right now with my new company, ScaleBase. Liran has posted 21 posts at DZone. View Full User Profile

Standard Query Language (SQL) for NoSQL databases?

08.12.2011
| 2490 views |
  • submit to reddit

I recently came across an interesting blog post on RedMonk (not surprising, as I read most of their posts). It’s called It’s Beginning to Look a Lot Like SQL and basically it talks about query language for NoSQL databases. It seems that as NoSQL becomes more popular, users want to do more with it – a good level of querying, for example, is needed.

Now of course, since NoSQL is a family of products that work in radically different ways, it’s not certain that this is possible (or even desirable – read Alex Popescu’s post on the subject).

But my question is – why do you even need a query language for NoSQL data stores? After all, running queries on distributed data might be complex to implement, and time consuming. The better architecture would look like this:

The application code is accessing NoSQL for primary key based access. Write operations go to NoSQL and MySQL, and complex queries (from the code, reporting, or BI systems) run with standard SQL (popular and familiar to most developers out there) against the MySQL database.

It’s a similar concept to Data Warehouse, only updates occur on the MySQL store in real time.

Now, of course, there are scaling and performance issues associated with running writes on MySQL, and that’s where ScaleBase fits in – as tt will allow MySQL to perform as required.

References
Published at DZone with permission of its author, Liran Zelkha. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)