Confirmed users
513
edits
Klahnakoski (talk | contribs) m (better read) |
Klahnakoski (talk | contribs) (Added code reference) |
||
| Line 17: | Line 17: | ||
* '''Metadata on dimensions and measures''' - ActiveData also provides context to the data it holds. It serves the purpose to allow exploration and discovery by third parties; by describing unit-of-measure, how dimensions relate to others, and provide human descriptions of the columns stored. This metadata is also invaluable in automating the orientation and formatting of dashboard charts: Knowing the domain of an axis allows code to decide the best (default) chart form, and provides logically reasonable aggregate options. | * '''Metadata on dimensions and measures''' - ActiveData also provides context to the data it holds. It serves the purpose to allow exploration and discovery by third parties; by describing unit-of-measure, how dimensions relate to others, and provide human descriptions of the columns stored. This metadata is also invaluable in automating the orientation and formatting of dashboard charts: Knowing the domain of an axis allows code to decide the best (default) chart form, and provides logically reasonable aggregate options. | ||
* '''Has a security model''' - Simpler applications can avoid the complications of a security model if it is baked into the ActiveData solution. If ActiveData is to become mainstream it is important that it can manage sensitive data and PII. | * '''Has a security model''' - Simpler applications can avoid the complications of a security model if it is baked into the ActiveData solution. If ActiveData is to become mainstream it is important that it can manage sensitive data and PII. | ||
= Code = | |||
Development is still in the early stages, and the code is not even working yet | |||
* Github: https://github.com/klahnakoski/ActiveData | |||
=Context= | =Context= | ||
| Line 44: | Line 49: | ||
==Non Solutions== | ==Non Solutions== | ||
ActiveData makes specific tradeoffs to achieve it's goals | ActiveData makes specific tradeoffs to achieve it's goals. It has the following limitations: | ||
* large memory requirements | * large memory requirements | ||
* low add/update/remove speeds | * low add/update/remove speeds | ||
* strict data model (snowflake schema, hierarchical relations only) | * strict data model (snowflake schema, hierarchical relations only) | ||
* non-relational | * non-relational | ||
* ETL work required to denormalize data | * ETL work required to denormalize data | ||
* ETL work required to provide dimension metadata | * ETL work required to provide dimension metadata | ||