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.
Post History
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 thin...
#2: Post edited
by
Michael
·
2024-04-08T19:04:44Z (about 1 month ago)
Proofreading. Add new tag. Searchable text for the tech elements.
integrating standalone database 'engine' into olap db
- Integrating a standalone database 'engine' into an OLAP database
i'm trying to build a proper understanding of what olap datastore vs olap data engine is. I tend to put too much value to keywords like "engine" vs "data store". If it has engine - I think it should be plugable into another tech stack.I found [this data tech](https://alirezasadeghi1.medium.com/open-source-data-engineering-landscape-2024-8a56d23b7fdb) landscape image.In the upper corner there is 2 categories - columnar olap database and olap engine.My background is in data engineering, so i automatically assume if a technology has 'engine' keyword - then it can be used as part of bigger olap db, because 'engine' means a smaller component.E.g. plugging engine pinot/druid as part of proper olap db - apache kudu.1.Is this assumption correct?2.what is the difference between olap database and olap engine?
- 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](https://alirezasadeghi1.medium.com/open-source-data-engineering-landscape-2024-8a56d23b7fdb) 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.
- 1. Is this assumption correct?
- 2. What is the difference between an OLAP database and an OLAP engine?
- [^1]: Online Analytical Processing
#1: Initial revision
by
erjcan
·
2024-04-08T17:59:44Z (about 1 month ago)
integrating standalone database 'engine' into olap db
i'm trying to build a proper understanding of what olap datastore vs olap data engine is. I tend to put too much value to keywords like "engine" vs "data store". If it has engine - I think it should be plugable into another tech stack. I found [this data tech](https://alirezasadeghi1.medium.com/open-source-data-engineering-landscape-2024-8a56d23b7fdb) landscape image. In the upper corner there is 2 categories - columnar olap database and olap engine.  My background is in data engineering, so i automatically assume if a technology has 'engine' keyword - then it can be used as part of bigger olap db, because 'engine' means a smaller component. E.g. plugging engine pinot/druid as part of proper olap db - apache kudu. 1.Is this assumption correct? 2.what is the difference between olap database and olap engine?