We have all our workloads on AWS.
We have all our workloads on AWS.
Having Teradata in AWS:
We had few reports which were taking more than 45 minutes. Then, with Teradata, we received results within minutes, and a few under a minute. We thought that something went wrong, and we hadn't done the work properly, but we saw the exact same results on both. So, our end users were pretty happy.
It is quick, secure, and has less hassles because we don't have to involve our networking team, infrastructure, etc. It is very easy to deploy and make market ready.
Teradata wants to come out of the hardware business and to run its own cloud on other public clouds. I think that is a great way to go. However, there are challenges to doing this. There are multiple layers of security and caching. E.g., if you have a lot of compute or a caching that will offload a lot of compute activity because it's already there, it will save its cycles for something which needs to be done. This way, you are offloading your compute, so you can go with a lesser capacity than a higher capacity. That is what this appliance does. If they are moving off of the appliance, I am curious to see if their software will withstand the change, or will Teradata still run but need a bigger box?
I would like more security and speed. These days, everyone is not just moving to cloud, but they are moving to clout. In a multi-cloud environment, you have to be cognizant of data transfer, bandwidth, and egress charges, not just from a performance and scalability point of view, but also how to keep costs low.
We haven't had any outages in one and a half years. That is a good statement.
I have not heard anyone complain about performance.
The technical support is pretty good. The response rate is good.
We had a bunch of legacy warehouses, which we wanted to consolidate, as well as stay up-to-date with warehousing options. This is why we moved into Teradata.
The integration and configuration were seamless for us.
We have multiple sources of data, so Teradata has a lot of connectors which pulls all our data from different workloads. The integration works really well.
We had help with the integration and configuration.
When your customer is happy, dollars and cents sort of blur. Our return on investment would be customer satisfaction, which I think is priceless.
We had a lot of parties involved when purchasing from the AWS Marketplace. They are very flexible and aggressive in trying to close the deal. They are good at what they have to offer and listening to the customer. It's a two-way street.
In this day and age, we want to get things done quickly. So, we go to the AWS Marketplace.
Also, we have a consistent experience with Teradata usage on its cloud, so we already know the product.
For what Teradata has to offer, their price is comparable to its competitors.
We evaluated Redis and Teredata, doing PoCs with both. We had more support from Teradata to start with, and we were new to both. We were not in a situation to tell which one was good, because both were new to us. We just had more support from Teradata to help us see the results on what we are looking for.
Do your homework before you make a decision. Everyone is different; every shop is different. That is what makes it fun to be in IT.
When you look for a solution, you will uncover many advantages. All those hidden things which are not clear initially when you do a cost analysis. A cost analysis is something that you have to do from the get-go, but it also has to be an ongoing process. Your workloads change, requirements change, everything changes, so it has to be a constant feedback.
We have used both the on-premise and AWS versions.