Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Integrating a standalone database 'engine' into an OLAP database
I'm trying to build a proper understanding of what an OLAP[1] datastore vs an OLAP data engine is. I tend to put too much value on keywords like "engine" vs "data store." If it has "engine," I think it should be pluggable into another tech stack.
I found a data engineering tech landscape chart on Medium with two OLAP categories in the top-right corner:
| Columnar OLAP Database | Real-Time OLAP Engine |
|---|---|
| Apache Kudu | ClickHouse |
| Greenplum Database | Pinot |
| MonetDB | Druid |
| DuckDB | Apache Kylin |
| Databend | Doris |
| ByConity | StarRocks |
| Hydra |
My background is in data engineering, so I automatically assume if a technology has the 'engine' keyword, then it can be used as part of bigger OLAP database, because 'engine' means a smaller component. E.g. plugging engine Pinot or Druid as part of proper OLAP database like Apache Kudu.
- Is this assumption correct?
- What is the difference between an OLAP database and an OLAP engine?
-
Online Analytical Processing ↩︎
0 answers
0 comment threads