Try our new research platform with insights from 80,000+ expert users

Amazon Aurora vs Teradata comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Jan 12, 2025

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Amazon Aurora
Ranking in Relational Databases Tools
10th
Average Rating
8.2
Reviews Sentiment
6.5
Number of Reviews
13
Ranking in other categories
No ranking in other categories
Teradata
Ranking in Relational Databases Tools
7th
Average Rating
8.2
Reviews Sentiment
7.0
Number of Reviews
76
Ranking in other categories
Customer Experience Management (4th), Backup and Recovery (20th), Data Integration (17th), Data Warehouse (3rd), BI (Business Intelligence) Tools (10th), Marketing Management (6th), Cloud Data Warehouse (6th)
 

Mindshare comparison

As of January 2025, in the Relational Databases Tools category, the mindshare of Amazon Aurora is 3.6%, down from 4.3% compared to the previous year. The mindshare of Teradata is 5.5%, up from 4.8% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Relational Databases Tools
 

Featured Reviews

Rajitha Jatothu - PeerSpot reviewer
Achieve high performance with fault-tolerant and highly available database management
Aurora is a key pillar for us, offering performance and availability. It is faster than RDS and supports multi-region clusters and scalability. One feature we value is Aurora's ability to provide a reader endpoint, allowing applications to connect without tracking replicas. It supports auto-scaling and offers several options for monitoring and optimizing database performance. Aurora's fault tolerance and ability to handle multiple replicas contribute to its reliability and high performance.
SurjitChoudhury - PeerSpot reviewer
Offers seamless integration capabilities and performance optimization features, including extensive indexing and advanced tuning capabilities
We created and constructed the warehouse. We used multiple loading processes like MultiLoad, FastLoad, and Teradata Pump. But those are loading processes, and Teradata is a powerful tool because if we consider older technologies, its architecture with nodes, virtual processes, and nodes is a unique concept. Later, other technologies like Informatica also adopted the concept of nodes from Informatica PowerCenter version 7.x. Previously, it was a client-server architecture, but later, it changed to the nodes concept. Like, we can have the database available 24/7, 365 days. If one node fails, other nodes can take care of it. Informatica adopted all those concepts when it changed its architecture. Even Oracle databases have since adapted their architecture to them. However, this particular Teradata company initially started with its own different type of architecture, which major companies later adopted. It has grown now, but initially, whatever query we sent it would be mapped into a particular component. After that, it goes to the virtual processor and down to the disk, where the actual physical data is loaded. So, in between, there's a map, which acts like a data dictionary. It also holds information about each piece of data, where it's loaded, and on which particular virtual processor or node the data resides. Because Teradata comes with a four-node architecture, or however many nodes we choose, the cost is determined by that initially. So, what type of data does each and every node hold? It's a shared-no architecture. So, whatever task is given to a virtual processor it will be processed. If there's a failure, then it will be taken care of by another virtual processor. Moreover, this solution has impacted the query time and data performance. In Teradata, there's a lot of joining, partitioning, and indexing of records. There are primary and secondary indexes, hash indexing, and other indexing processes. To improve query performance, we first analyze the query and tune it. If a join needs a secondary index, which plays a major role in filtering records, we might reconstruct that particular table with the secondary index. This tuning involves partitioning and indexing. We use these tools and technologies to fine-tune performance. When it comes to integration, tools like Informatica seamlessly connect with Teradata. We ensure the Teradata database is configured correctly in Informatica, including the proper hostname and properties for the load process. We didn't find any major complexity or issues with integration. But, these technologies are quite old now. With newer big data technologies, we've worked with a four-layer architecture, pulling data from Hadoop Lake to Teradata. We configure Teradata with the appropriate hostname and credentials, and use BTEQ queries to load data. Previously, we converted the data warehouse to a CLD model as per Teradata's standardized procedures, moving from an ETL to an EMT process. This allowed us to perform gap analysis on missing entities based on the model and retrieve them from the source system again. We found Teradata integration straightforward and compatible with other tools.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"Aurora is a key pillar for us, offering performance and availability."
"We had better control over the parameters that we could tweak in terms of intermediate storage and better indexing capabilities."
"Aurora's compatibility with MySQL or PostgreSQL benefited our database management. The migration from on-premise MySQL to Aurora was similar, so we didn't need to change our source code."
"Aurora's features that I find the most beneficial include its database backup strategy, performance options, and input-output operations."
"The most valuable feature is the ability to do multiple-read and single-write. These are the kinds of features that we were interested in, and Aurora takes care of that natively."
"The solution’s scalability is good since we don’t need to take a maintenance window during unpredictable workloads. I like the solution’s behind-the-scenes happenings. It is a great feature."
"The most valuable feature of Amazon Aurora is SQL standardization, it doesn't have its own syntax which is good. It has a lot of hands-off self-management type of activities, such as log rolling and auto-scaling."
"The provision of custom read and write endpoints eliminates the need for managing a separate proxy load balancer."
"Viewpoint, the detailed query logs and performance statistics are valuable features."
"IntelliFlex is easy to scale - one of its best features is that you can upscale it to the size you want."
"Teradata effectively uses parallelism to the granular level, performing better than other databases."
"There are several features of Teradata that I like. One of the most basic is the indexes. I also like that it provides lower TCO. It also has the optimizer feature which is a good feature and isn't found in other legacy systems. Parallelism is also another feature I like in Teradata because when you are running or hosting on multiple systems, you have this shared-nothing architecture that helps. Loading and unloading in Teradata are also really helpful compared to other systems."
"It's very mature from a technology perspective."
"The most valuable features of Teradata are that it is a massively parallel platform and I can receive a lot of data and get the queries out correctly, especially if it's been appropriately designed. The native features make it very suitable for multiple large data tasks in a structured data environment. Additionally, the automation is very good."
"It has massive parallel processing ability to do large amounts of concurrent querying."
"Teradata can be deployed on-premise, on the cloud, or in a virtual machine, which means customers can move without having to create their architecture all over again."
 

Cons

"Room for improvement might be in the UI, integrations, or data working capabilities for better user experience."
"I would like to see more AI-related features in future releases."
"It is a bit costly. The features are quite good, and I wouldn't say it requires any technical improvements. But from a cost perspective, some clients wouldn't go for Aurora because of that."
"The product's distributed query process for MySQL needs improvement."
"I would like to see performance insights on the database based on the queries. Currently, we use SolarWinds as the monitoring tool. I would like to leverage SolarWinds’ performance insights in AWS services. SolarWinds gives larger insights when we run performance issues."
"The pricing could improve. It should be reduced."
"While Amazon Aurora meets your current scaling and storage needs, there is room for improvement in cryptography and scalability compared to other databases."
"It would have been helpful if they had provided some benchmarking numbers."
"Teradata has a few AI models, but in data science, we need more flexibility."
"There is a need to improve performance in high transaction processes, as well as the reporting system."
"They should add more connectors to different platforms."
"We tried to use case Teradata for a data warehouse system, but we had some problems in relation to the Teradata system, CDC tools, and source databases. We were unable to transfer data from HPE Integrity mainframe to Teradata."
"Limited interest and success in some areas make us hesitate about upgrading."
"The user interface needs to be improved."
"The setup is not straightforward."
"Teradata is somewhat late in adopting cloud technology."
 

Pricing and Cost Advice

"The price could be lower compared to its competitors."
"There is no need to buy a license for the product. We can pay as per the use case."
"It is quite expensive."
"The tool’s pricing depends on the instance type. For cost optimization purposes, we use the result instance category."
"It is an expensive solution."
"I would rate the pricing a six out of ten, with ten being expensive."
"It comes at a notably high cost for what it offers."
"Teradata's licensing is on the expensive side."
"Make sure you have the in-house skills to design and support the solution, as relying on external sources is extremely costly and tends to lock you into specific platforms, tools, and paradigms."
"Users have to pay a yearly licensing fee for Teradata IntelliFlex, which is very expensive."
"The price of the solution could be reduced, it is expensive."
"In the past, it turned out that other solutions, in order to provide the full range of abilities that the Teradata platform provides plus the migration costs, would end up costing more than Teradata does."
"The price needs to be more competitive as Hadoop, Redshift, Snowflake, etc are constantly making way into EDW space."
"Teradata is not cheap, but you get what you pay for."
report
Use our free recommendation engine to learn which Relational Databases Tools solutions are best for your needs.
830,824 professionals have used our research since 2012.
 

Comparison Review

it_user232068 - PeerSpot reviewer
Aug 5, 2015
Netezza vs. Teradata
Original published at https://www.linkedin.com/pulse/should-i-choose-net Two leading Massively Parallel Processing (MPP) architectures for Data Warehousing (DW) are IBM PureData System for Analytics (formerly Netezza) and Teradata. I thought talking about the similarities and differences…
 

Top Industries

By visitors reading reviews
Financial Services Firm
28%
Computer Software Company
14%
Government
5%
Manufacturing Company
5%
Financial Services Firm
26%
Computer Software Company
10%
Manufacturing Company
8%
Healthcare Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about Amazon Aurora?
Aurora's compatibility with MySQL or PostgreSQL benefited our database management. The migration from on-premise MySQL to Aurora was similar, so we didn't need to change our source code.
What is your experience regarding pricing and costs for Amazon Aurora?
The price of Aurora is generally reasonable. It fluctuates based on performance levels and usage, yet maintains a good balance with our operational demands.
What needs improvement with Amazon Aurora?
Currently, I am unsure what aspects of Aurora require improvement. The solution meets our needs in terms of high availability, durability, and backups. However, room for improvement might be in the...
Comparing Teradata and Oracle Database, which product do you think is better and why?
I have spoken to my colleagues about this comparison and in our collective opinion, the reason why some people may declare Teradata better than Oracle is the pricing. Both solutions are quite simi...
Which companies use Teradata and who is it most suitable for?
Before my organization implemented this solution, we researched which big brands were using Teradata, so we knew if it would be compatible with our field. According to the product's site, the comp...
Is Teradata a difficult solution to work with?
Teradata is not a difficult product to work with, especially since they offer you technical support at all levels if you just ask. There are some features that may cause difficulties - for example,...
 

Comparisons

 

Also Known As

No data available
IntelliFlex, Aster Data Map Reduce, , QueryGrid, Customer Interaction Manager, Digital Marketing Center, Data Mover, Data Stream Architecture
 

Overview

 

Sample Customers

Dow Jones, Arizona State University, Verizon, Capital One, United Nations, Nielsen, Autodesk, Fanduel
Netflix
Find out what your peers are saying about Amazon Aurora vs. Teradata and other solutions. Updated: January 2025.
830,824 professionals have used our research since 2012.