← All public trees

Decision Trees by M&AOperatingSystem

M&AOperatingSystem has published 3 public decision trees on Draw Decision Tree. Each one is an interactive wizard you can run in your browser or embed in your own site.

Published trees

Which API design pattern is right for my project?

Determine the right API design style for your integration scenario.

Practical Data: How many Layers Do I need?

This decision tree is aimed at Chief Data Officers (CDO) and Senior Technical Architects trying to figure out the right medallian style architecturedata warehouse product manager responsible for figuring out the most appropriate mechanism for integrating new data sources to a four-tier data warehouse, use this decision tree to identify the most effectivel integration strategy possible. The tool presumes three architecture principles - i) all data consumption takes place from the final data products layer and ii) The further to the "right" the integration takes place towards platinum, the more efficient the technology data processing (ie less storage and less compute) iii) Finally we prefer to materialise data as views over adding addition storage layers.

Practical Data: Which Layer should I Integrate to?

As a data warehouse product manager responsible for figuring out the most appropriate mechanism for integrating new data sources to a four-tier data warehouse, use this decision tree to identify the most effective integration strategy possible. The tool presumes three architecture principles - i) all data consumption takes place from the final data products layer and ii) The further to the "right" the integration takes place towards platinum, the more efficient the technology data processing (ie less storage and less compute) iii) Finally we prefer to materialise data as views over adding addition storage layers.

All trees by M&AOperatingSystem

• Which API design pattern is right for my project? — Determine the right API design style for your integration scenario.
• Practical Data: How many Layers Do I need? — This decision tree is aimed at Chief Data Officers (CDO) and Senior Technical Architects trying to figure out the right medallian style architecturedata warehouse product manager responsible for figuring out the most appropriate mechanism for integrating new data sources to a four-tier data warehouse, use this decision tree to identify the most effectivel integration strategy possible. The tool presumes three architecture principles - i) all data consumption takes place from the final data products layer and ii) The further to the "right" the integration takes place towards platinum, the more efficient the technology data processing (ie less storage and less compute) iii) Finally we prefer to materialise data as views over adding addition storage layers.
• Practical Data: Which Layer should I Integrate to? — As a data warehouse product manager responsible for figuring out the most appropriate mechanism for integrating new data sources to a four-tier data warehouse, use this decision tree to identify the most effective integration strategy possible. The tool presumes three architecture principles - i) all data consumption takes place from the final data products layer and ii) The further to the "right" the integration takes place towards platinum, the more efficient the technology data processing (ie less storage and less compute) iii) Finally we prefer to materialise data as views over adding addition storage layers.

About Draw Decision Tree

Draw Decision Tree is a free tool for building, visualizing, and embedding interactive decision trees using a human-readable DSL. Start building your own →