Agora on AWS

My main use case for Denodo  is that we have very decentralized data sources from different legacy applications, so this tool is very useful for us to connect all these legacy systems. This tool is very helpful for our data discovery and mapping. Getting real data from APIs and combining data from multiple systems were major challenges, which were solved by Denodo  within a minimum replication cost.

A specific example of how Denodo helped me connect those legacy systems is that this tool is very easy to use and supports a multi-database infrastructure. We have a very large enterprise and we are blending data across the enterprise. What Denodo has helped us achieve is both federated and non-federated data with the same reusable data structure.

Regarding my main use case with Denodo, I also use it to build and send our data service to our partners and stakeholders and provide a real-time data experience to them. It is really easy to use, fast, and secure. Additionally, it is possible to combine many sources of data and integrate them with one tool.

The best features Denodo offers stand out to me as the ability to develop REST web services fast and easily, create and combine new views, integrate different sources of data, and connect with other tools seamlessly.

When I mention fast and easy creation of views and integration, I love the agile data provisioning and integration, where Denodo provides a comprehensive set of capabilities for implementing logical data integration, management, and delivery, which in turn enables agile data analytics and an informed decision-making process to be smooth. I also appreciate the performance optimization with AI, which improves performance optimization through the integration of artificial intelligence capabilities. Furthermore, I appreciate the unified security and governance, where it addresses the need for an organization to effectively manage security, data privacy, and data protection easily, offering a centralized platform that allows the application of governance policies and fine-grained security controls.

Another feature I would add about Denodo is that it also provides a single point of control where we can establish security controls over the entire infrastructure and gain visibility into all our data assets.

Denodo has positively impacted my organization as since we started using this tool, it has been very helpful because it is a huge advantage that we can connect to many different databases to provide data rapidly and accurately and also gain insights, which helps us to make data-driven decisions easily. It has proven to be a valuable environment for deploying data virtualization solutions, and its user community is active in finding and fixing issues more accurately.

Through data insights from Denodo, we have been able to improve our decision making, which helps to better communication between the stakeholders thanks to the real-time experience. It also saves a lot of time.

Denodo can be improved as it can be a little buggy, especially when dealing with huge data and is not great if you have very large volumes of data because it can be buggy.

To add more about the needed improvements for Denodo, I think the user interface should be improved to be more user-friendly and intuitive, especially for those new users who find the learning curve a bit steep.

I have seen a positive return on investment for one client who was paying too much for an existing legacy reporting platform that has not been updated in decades. For another client that did not have any traditional BI tools, Denodo is the perfect tool. It provides a positive experience for end users who can now run reports using multiple near real-time data sources, and a positive return on investment for those who can connect multiple data sources and make data-driven decisions easily.

The reason why we switched from Cisco Composite to Denodo is that we evaluated other data visualization platforms such as Cisco Composite and found that Composite had an even smaller community and less support than Denodo. Denodo is putting a lot of the revenue earned from licensing cost to grow the product, and we did not get that impression from Composite.

The advice I would give to others looking into using Denodo is that it is very well suited for large organizations with siloed datasets. Denodo thrives in these environments since large organizations can afford the licensing cost and are always tasked to mash up data from multiple environments through the organization. It helps to make data-driven decisions more easily and is very cost-effective, so I highly recommend it as a tool. I would rate this product a 9 out of 10.

My main use case for Denodo  is jobs which I require for test data, so that is one place where Denodo  has come in. I think we have to write SQL queries, and there are cases where there are AWS  Redshift databases. There is a difference in query results that we have to validate between legacy and modern systems, which is one of the use cases. Then when we test using Rest Assured or using Postman, there is a layer of Denodo that comes into play.

I can tell you about a specific example where Denodo made a difference in one of my test data or validation projects. We had a case in one of the projects where we had a large number of APIs that were sequentially connected with each other. What exactly was happening there was that there was a UI developed, then there was this API, and several AWS  services which we were working with together. Denodo came into the picture because there were some masking and security-related customer emails on local QA environments. So there was a use case of real data where we could not really scrub the database. Denodo had an implementation there.

The best features Denodo offers in my experience include a very solid compatibility with AWS and AWS Athena . Denodo also works with EC2  auto-scaling groups, so the scalability aspects are excellent. Denodo is installable via AWS Marketplace  directly, and that installation part is seamless.

Denodo has positively impacted my organization, and I have noticed changes since its implementation. The performance of our application has increased significantly. Earlier, we used to have several outages or slowness that users reported, but now those things do not happen.

I can share specific outcomes or metrics. Latency was one of the metrics being tracked, and we were at double nines sort of accuracy in latency. The latency slowed down by a factor of about ten altogether, which was a key metric observed after Denodo was implemented.

Denodo can be improved in some areas. We faced some issues with respect to Java client dependencies and had significant hassle with version management. Improving version management is something Denodo can work on.

I have been using Denodo for close to two years, on and off in two different organizations.

Denodo is totally stable in my experience.

The scalability of Denodo specifically helped my team or projects in situations where it made a big difference. We had one application deployed on a multi-continent system where several different countries used the application at the same time. The application was taking performance hits and slowing down at times. Denodo's scalability comes into play specifically when there is data transfer.

Denodo's scalability is good. It scales well, and I scaled it across two continents and four countries with very few issues.

I have not interacted with customer support.

The company did purchase Denodo through the AWS Marketplace , although not me personally.

My experience with pricing, setup cost, and licensing is that licenses were bought at an aggregate level from a vertical, which had significant costs. However, I am not sure about the specific pricing and setup cost, as these were centrally handled.

I have seen a return on investment, which showed up in improved customer satisfaction scores. It was not exactly about money or time saving, but the customer scores did improve.

I think Denodo was the top choice, and my organization did not evaluate other options before choosing it.

On a scale of one to ten, I would rate Denodo a seven. I gave it a seven because it was not held back or anything. We had a very limited use case as QEs, and we used it as a supporting layer or an intermediate layer. It was more useful towards teams that had dedicated performance reduction goals that we did not have, so it was all good to me.

My advice for others looking into using Denodo is that if you have multi-country applications, latency, and slowness and are looking to optimize queries for better performance at a backend layer, especially with many APIs or microservices, Denodo is the solution to choose.

I have no additional thoughts about Denodo before we wrap up as I think I have shared everything. I would rate Denodo a seven out of ten.