4 ms·
As an end-user of databases, I hope in 50 years time, there will be no meaningful distinction between OLAP and OLTP DBs. We spend so much time and energy copyi
by iamEAP 7y ago
As an end-user of databases, I hope in 50 years time, there will be no meaningful distinction between OLAP and OLTP DBs.
We spend so much time and energy copying data around into specific data stores to solve specific problems / answer specific questions / enable specific features... It's messy, complex, and adds a ton of overhead.
It could simplify a lot of technology if an operational database could also handle non-trivial analytical workloads.
- carlineng 7y agoThis would be amazing, but it's an open question in my mind if it's possible to have a system that works sufficiently well for both OLTP and OLAP use cases at large scale. HTAP systems today are still very raw, and it intuitively feels like we'll be bumping into the Pareto frontier, where optimizing for analytics use cases can only come at the expense of transactional performance.
- hbk 7y agoGoogle Cloud Spanner kind of does what you want.
- georgewfraser 7y agoYou’re not going to run your analytical queries off your production DB once you have more than a couple users writing ad-hoc queries. And you probably don’t won’t to replicate your salesforce/ads/clicks into your prod db. So you’re going to create a replica. So why does it matter if the replica is a different type of database than prod?
- pintxo 7y agoIsn't this the promise made by SAP HANA?
- mathh 7y agoOracle Active Data Guard also (queriable replica), with column store.
- hinkley 7y agoDo any current databases support replicas with heterogeneous indexes? It seems like that would greatly reduce this problem.