The ICDE 2016 finished more than a month ago, and unfortunately I didn’t post even a half of the things I wanted to post about the conference. In the next couple of days I will try to explain why it happened (although some of my friends already know). But there was one topic I really wanted to cover, so I decided to finish this blog post even six weeks later.
OK, I understand that that’s a buzz word these days. Moreover, I am even aware of a limited number of situations, when using a NoSQL makes sense. But it bugs me immensely when I hear something to the effect yea, it’s not much you can do with the traditional RDBMS, in order to achieve high performance you need to switch to NoSQL. These statements are related to “oh, you need to build a Datamart – then you need to use Redshift! It’s specifically designed for datamarts! Or – when I was trying one third – party software about a month ago trying to see whether it will help me to consolidate data from different sources, I’ve realized while observing the error messages that they were using Hadoop in between!
So – when I was listening to the presentation NoSE: Schema Design for NoSQL Applications from the University of Waterloo, I could not stop wondering… The presentation was about creating virtual schemas for the noSQL framework, and the presented was and at the end I’ve asked the question. Or rather I made a statement:): I remember the times, when the relational databases were not the industry standard. I remember the times, when you would try to predict which queries would be the most frequent and model you sets or you hierarchy accordingly. And I also vividly remember, how horrible it was when it didn’t work right, and thereby I remember exactly what was the reason everybody embraced the relational model.
So my question is – why we go back in time?
You know what was interesting? That a number of participants of different age and different background approached me after this session and expressed their full support :))