Sign in Agent Mode
Categories
Your Saved List Become a Channel Partner Sell in AWS Marketplace Amazon Web Services Home Help

Denodo 9 Enterprise Plus

Denodo Technologies Inc.

Reviews from AWS customer

2 AWS reviews

External reviews

12 reviews
from

External reviews are not included in the AWS star rating for the product.


3-star reviews ( Show all reviews )

    reviewer2787339

Improved test data validation and latency has revealed client dependencies that still need refinement

  • January 16, 2026
  • Review from a verified AWS customer

What is our primary use case?

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.

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

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

What do I think about the stability of the solution?

Denodo is totally stable in my experience.

What do I think about the scalability of the solution?

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.

How are customer service and support?

I have not interacted with customer support.

How would you rate customer service and support?

How was the initial setup?

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

What about the implementation team?

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.

What was our ROI?

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.

Which other solutions did I evaluate?

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

What other advice do I have?

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.

Which deployment model are you using for this solution?

Private Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Amazon Web Services (AWS)


showing 1 - 1