In Part 1 of this post I covered the NoSQL movement, and described what I think is not ideal there.  A short recap would be the following points:

1. Lack of standardization – each database provides its own API and query language, that is  often tightly coupled with its implementation.
2. “No fancy queries” – users need to write their own de-normalization routines outside the database, which is prone to errors.
3. Data migration – de-normalized data more sensitive to software updates than normalized data.  As a result, more throw-away code needs to be written just to perform data migrations.

In this post I will present what I call NoDatalog, and explain how it can, at least in theory, overcome these three issues.Read More »

In this post I’ll talk about NoSQL, what it is, why it is important, and what is wrong about it.  In Part 2 I’ll present and alternative: a new concept that my co-author and I coined in a recent paper: NoDatalog, and explain how it can give us the benefits of NoSQL, but without the disadvantages (at least in theory…)Read More »