Denodo is the eponymous data integration platform from the global company headquartered in Silicon Valley.
N/A
Mage
Score 8.6 out of 10
N/A
Mage is a tool that helps product developers use AI and their data to make predictions. Use cases might be predictions for churn prevention, product recommendations, customer lifetime value and forecasting sales.
Denodo allows us to create and combine new views to create a virtual repository and APIs without a single line of code. It is excellent because it can present connectors with a view format for downstream consumers by flattening a JSON file. Reading or connecting to various sources and displaying a tabular view is an excellent feature. The product's technical data catalog is well-organized.
Mage is well-suited for probability score for uptake of every product is calculated for customers using ML/ Regression models, choosing customers for a product/ Top products for a customer, based on the requirement and Identifying popular product combinations using association rules from Market Basket Analysis (or affinity Analysis)\Bundle these products as combos.
Caching - but I am sure it will be improved by now. There were times when we expected the cache to be refreshed but it was stale.
Schema generation of endpoints from API response was sometimes incomplete as not all API calls returned all the fields. Will be good to have an ability to load the schema itself (XSD/JSON/Soap XML etc).
Denodo exposed web services were in preliminary stage when we used; I'm sure it will be improved by now.
Export/Import deployment, while it was helpful, there were unexpected issues without any errors during deployment. Issues were only identified during testing. Some views were not created properly and did not work. If it was working in the environment from where it was exported from, it should work in the environment where it is imported.
Denodo is a tool to rapidly mash data sources together and create meaningful datasets. It does have its downfalls though. When you create larger, more complex datasets, you will most likely need to cache your datasets, regardless of how proper your joins are set up. Since DV takes data from multiple environments, you are taxing the corporate network, so you need to be conscious of how much data you are sending through the network and truly understand how and when to join datasets due to this.
Mage was the easiest in terms of ease of implementation due to its no-code functionality. However, Mage doesn't have a whole ecosystem like AWS and slightly falls behind there.
