I'd like to pitch an idea:
Superset and Cubes have complementary goals, while Superset is focused on Presentation
Cubes provides the underlying Model and View layer.
# What is Cubes (in a nutshell)?
Cubes is a light-weight Python framework and set of tools for Online Analytical Processing (OLAP),
multidimensional analysis and browsing of aggregated data. Focus on data analysis, in human way.
Purpose is to provide a framework for giving analyst or any application end-user understandable
and natural way of presenting the multidimensional data.
One of the main features is the logical model,
which serves as abstraction over physical data to provide end-user layer.
Features:
- OLAP and aggregated browsing (default backend is for relational databse - ROLAP)
- multidimensional analysis
- logical view of analysed data - how analysts look at data, how they think of data,
not not how the data are physically implemented in the data stores
- hierarchical dimensions (attributes that have hierarchical dependencies,
such as category-subcategory or country-region)
- localizable metadata and data
- SQL query generator for multidimensional aggregation queries
- OLAP server – HTTP server based on Flask Blueprint,
can be easily integrated into your application.
# Why Cubes for Superset?
Currently Superset does only support OLAP Cubes on top of Druid.io and `raw SQLAlchemy`.
# What would be the advantages for Cubes?
- An out of the box powerful visualization solution.
- Access to the huge and growing Superset community
- Increased visibility which may attract more contributors to cubes
# What are the advantages for Superset?
- access to an opensource lightweight (R)OLAP server built in python
(which seems an ideal match as Superset itself is built in python)
- support OLAP out of the box without the need for Druid.io
# Where to start an integration?
are examples for Druid and SqlAlchemy connectors.
Superset Connectors seem a to be good match to be built with Expressions