I think that's the point. The idea that you need a different database for OLTP vs OLAP, vs whatever is a technological one. Not a conceptual one. Operationally,

I think that's the point. The idea that you need a different database for OLTP vs OLAP, vs whatever is a technological one. Not a conceptual one. Operationally, if you had the freedom you'd ideally like to have just one database that can handle everything, storing data in appropriately accessible formats (relational, time-series. key-value, document, etc). This is getting commodity open source databases up to that level of "don't care, it's fast enough" for OLTP. Then on to all the other workloads. Think of it like the move from C/C++ to dynamic languages like python or lisp as cpu's got faster. Cool beans.