Amazon Aurora Reviews & Insights

Amazon Aurora comes with an easy to use and intuitive workflow. Our business started using Amazon Aurora to handle vast websites with huge content and file systems. We nearly have 500+ websites and all of them use Amazon Aurora. As far as I know, everything has been seamless until now. Of course there were hiccups in the between with some outages but were handled by Amazon Aurora support very well.

We have around 500+ websites in which we are using Amazon Aurora. Most of them are huge in terms of content and transactions per minute that the databases handle. In my opinion, database encryption is well defined. It automatically upsizes, upscales the clusters that it provides per database.
Once we had an outage for around 30hours. We have one website which sends around 1.5k files at a time monthly to another vendor using the database. We had an outage once and had a backlog of around 12k files not being sent to our other vendor. But, support team was readily available in shifts the whole time, they passed on notes of what and how much work is done to their colleagues and resolved the issue within 30hours (which would have easily taken 4-5 working days to understand) for us.

My organization uses Amazon Aurora as a database to store customer request information at scale. We also scan the database at a minimum of every 10 minutes to produce telemetry towards insights on customer usage

reasonable resource for large scale with more defined schema. Users should avoid if your schema updates often

We are using native Amazon Aurora for several customers in his version of mysql and Postgres.

We use Amazon Aurora for Wordpress insatance in E Commerce portals

I really like Amazon Aurora for use as an db for an instance of Wordpress.

I think the performance is really good especially when you use it in a transactional use case.

Amazon Aurora is characterized by high availability and performance in the cloud that few tools of the same characteristics offer, the cost is initially 10GB for free, but then costs increase but the amount of capacity used, however it can be really low and its use guarantees integrated security, with regular backups and fully protected by the Amazon Aurora system. It's a fully managed system which reduces the workload and automates many daily tasks that would take a lot of time to perform manually. Another important point to take into account is that the tool automatically recovers from any failure, if one of our instances fails the system uses replicas to repair them creating new instances automatically.

I think Amazon Aurora is well suited in the database arena. Amazon Aurora abstracts the connections of the database instances relationships, with a sophisticated link point mechanism, achieving more speed when processing intermediate data, which is extremely positive for large volumes of data that need to be processed quickly. In my experience, Amazon Aurora is a powerful tool when replicating data, since it manages everything in its platform with read-only queries.

Amazon Aurora just works.My experience with Amazon Aurora has been nothing but excellent. The Aurora database platform has been easy to deploy, configure, monitor, and maintain, and its performance capabilities have been able to handle any amount of workload we've thrown at it.

We are using Amazon Aurora (Postgres) for Mission-critical databases.

Aurora well suits for application which is having active-passive setup, and not advisable for active-active applications.

Amazon Aurora is a great product as it provides us with a cloud-native DB that provides MySQL and Postgres compatibility while simultaneously offering all the benefits of a cloud-native product - built-in security, continuous backups, serverless computing, and high integration with other AWS Services. It is ideal for powering a number of web applications based on the LAMP or LAPP stack.

Amazon Aurora is ideal for applications running in the well-known LAMP or LAPP stacks. It's generally great and the benefits of cloud-native elasticity, scale, security, ease to set up replicas and backups, and so on make it ideal for web-based applications. However, you need to be a tiny bit careful when using Aurora - and this is true for all products that generally emulate/simulate products. Generally, the more strange or exotic MySQL or Postgres features you are using, the more problems you're going to have with Aurora. However, as most LAMP/LAPP stacks aren't generally too exotic these tend to be edge cases that can be coded in other fashions.

We use Aurora as the de-facto DBaaS product for hosting our Relational Databases, primarily MySQL. We have over 100 MySQL clusters (Master, Slave) across the microservices and the 5 global regions where Capillary's SaaS products are hosted. Prior to Aurora, all our databases were self-managed and hosted on EC2 instances with EBS volumes, having provisioned IOPS, for storage. As our system scaled, the management of the databases became a full-time job. Also, configuration management, upgrades, and regular maintenance started eating into the team's bandwidth. Furthermore, the chances of human errors and the consequent outages increased with the increase in the number of MySQL set-ups. To address these concerns, in early 2020, we migrated all our MySQL clusters from EC2 to Aurora. The Aurora service hosts over 400 TB of data, and the Aurora instances vary from 4 cores, 32GB RAM to 32 cores, 256 GB RAM configs. The storage layer varies anywhere from 200GB to 30 TB. In a nutshell, all relational, OLTP use-cases for the 700M odd end-consumers touched by Capillary's platform and served out of Aurora.

Well Suited: If you have to manage 10 or more MySQL clusters in your environments. Better to use Aurora and configure via a Terraform provider. Don't have to worry about the scalability of your databases. It scaled beautifully with tons of features that make the scaling process easier. Don't have a dedicated infrastructure team. Use the managed service, and let your developers focus on product development.

Less Appropriate: It can be a bit pricey. If you are operating under a budget, this may not be the right tool. RDS is slightly cheaper than Aurora. Configurations and documentation can be confusing at times, but if you have access to the AWS Solution Architects, it gets easier.

Aurora is our SQL solution for users, events, articles, and more. Aurora provides convenient scaling and availability in different physical locations.. The security and scaling are automated to support peaks in traffic and save money when it's quiet. The integration with other AWS services makes it convenient for us to use in all applications. The SQL language support made the migration from a dedicated MySQL server seamless in our codebase.

It is best suited when you need an easily manageable auto-scaling relational database cluster in different secure locations on Amazon Web Services and not best suited when you're not using Amazon Web Services or you are seeking a cheaper option for testing only or for low traffic sites, or you require a NoSQL database instead.