Denodo - do no delays
Overall Satisfaction with Denodo
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.
- Improved time-to-market. We addressed new requirements in less than 2 person days.
- Very agile. Easy to handle changing requirements. Like a new requirement, a change in requirement was not expensive either.
- Platform issues were difficult to diagnose and debug.
I did not use any other data virtualization platform. BizTalk is not the right comparison; it is an integration layer and for orchestration; do not use denodo as an orchestration layer, it is not for connecting upstreams to downstreams and orchestrate data flows, it is primarily for pulling information and presenting in a fashion that benefit the audience.
Comments
Please log in to join the conversation