It is the database service where the main application writes its data. Any processing from the front end is typically stored in Aurora unless the data is object-oriented, in which case it is logged into MongoDB.
EVP Technology at a consultancy with 51-200 employees
Real User
Top 5
2023-05-03T07:07:00Z
May 3, 2023
We had challenges in loading huge volumes of data quickly, with reports growing beyond a certain number of millions of rows. Despite indexing and applying filters, we experienced significant latency loading the related reports. That's why we looked into using Aurora. We monitored it for about six months and tweaked the database-related parameters, but we still didn't see much improvement. So we reverted to RDS.
Owner at a computer software company with 1-10 employees
Real User
Top 20
2023-02-17T13:34:26Z
Feb 17, 2023
I am using Amazon Aurora as a relational database. Our applications for our business users are usually relatively internal application types which are mostly small, which makes data storage and retrieval quick and easy, especially when developing business applications where time is of the essence. Therefore, it is preferable to have a technology that allows developers to work quickly and seamlessly, without any complicated setup or extra steps. When we use NoSQL databases the data comes at a high speed.
Amazon Aurora is a relation database built on top of a Postgre or MySQL engine. These days, we are mostly developing small microservices, and we consider Aurora if we want to have a scalable database. It can have a higher number of read replicas. In those instances, we recommend Aurora. With one or two projects, we have used Aurora. The solution is deployed on their managed service on the cloud.
Amazon Aurora is a MySQL and PostgreSQL-compatible relational database built for the cloud, that combines the performance and availability of traditional enterprise databases with the simplicity and cost-effectiveness of open source databases.
Amazon Aurora is up to five times faster than standard MySQL databases and three times faster than standard PostgreSQL databases. It provides the security, availability, and reliability of commercial databases at 1/10th the cost. Amazon Aurora is...
It is the database service where the main application writes its data. Any processing from the front end is typically stored in Aurora unless the data is object-oriented, in which case it is logged into MongoDB.
I use Aurora for data storage.
I use Amazon Aurora for the high availability of MySQL cluster solutions.
We had challenges in loading huge volumes of data quickly, with reports growing beyond a certain number of millions of rows. Despite indexing and applying filters, we experienced significant latency loading the related reports. That's why we looked into using Aurora. We monitored it for about six months and tweaked the database-related parameters, but we still didn't see much improvement. So we reverted to RDS.
The solution is auto-scalable and serverless. It runs on the background and automatically scales up incase of heavy loads.
I am using Amazon Aurora as a relational database. Our applications for our business users are usually relatively internal application types which are mostly small, which makes data storage and retrieval quick and easy, especially when developing business applications where time is of the essence. Therefore, it is preferable to have a technology that allows developers to work quickly and seamlessly, without any complicated setup or extra steps. When we use NoSQL databases the data comes at a high speed.
Our deployment was only used within the organization. We didn't make it available publically.
Amazon Aurora is a relation database built on top of a Postgre or MySQL engine. These days, we are mostly developing small microservices, and we consider Aurora if we want to have a scalable database. It can have a higher number of read replicas. In those instances, we recommend Aurora. With one or two projects, we have used Aurora. The solution is deployed on their managed service on the cloud.