Denodo - do no delays
Rating: 7 out of 10
IncentivizedUse Cases and Deployment Scope
Denodo was used by the engineering team. It helped with mashing complex data structures from disparate sources and providing a JDBC wrapper for the result set. It simplified business needs that were difficult projects otherwise. The company's proprietary UX software exposed the data in grids and enabled analytics on mashed up data. It enormously benefited the executives to be able to correlate key information and visualize reports in seconds that otherwise were too laborious.
Pros
- Flat learning curve.
- Does not need brilliant developers.
- Less need for custom denodo wrappers, even if needed is not very complex.
- Denodo stored procedures and functions helped address complex, not straightforward requirements.
- Export/import deployment between environments was very helpful.
Cons
- 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.
Likelihood to Recommend
Denodo is a data virtualization software that works on real-time data. Choose it when you do not want to have a local storage or replication.
1. Do you need to mashup data from different datasources returning different types of data at real-time? Denodo works here.
2. Do you need to do data aggregation and run reports on local data? Denodo may not be the best fit.
3. Do you want a wrapper for your database and expose as webservices? Maybe Denodo can fit. However this is purely based on business needs.
4. Do you want to use Denodo as a caching layer? Maybe Denodo is not suited for this. You have to look at specific caching solutions.
5. Is time-to-market a key factor? Integrating two sources was a cakewalk with Denodo. It is a compromise of cost vs. time-to-market.
6. How frequently will you need to integrate another datasource or a new data set? One time integration may be best to achieve outside of Denodo or any data virtualization platform for that matter.
1. Do you need to mashup data from different datasources returning different types of data at real-time? Denodo works here.
2. Do you need to do data aggregation and run reports on local data? Denodo may not be the best fit.
3. Do you want a wrapper for your database and expose as webservices? Maybe Denodo can fit. However this is purely based on business needs.
4. Do you want to use Denodo as a caching layer? Maybe Denodo is not suited for this. You have to look at specific caching solutions.
5. Is time-to-market a key factor? Integrating two sources was a cakewalk with Denodo. It is a compromise of cost vs. time-to-market.
6. How frequently will you need to integrate another datasource or a new data set? One time integration may be best to achieve outside of Denodo or any data virtualization platform for that matter.