Amazon Aurora Deep Dive: Design, migration from RDS, and cost optimization [Cloud Masters

[@baligo3760]

Interesting content, thank you! Couple of times I had performance issues with Aurora Mysql. I tried increasing the class of the db instance, I also tried adding read replica but it didnt help at all - the app was running long queries without parallelism and it was only using one core of the RDS so the more powerful instance did not change the times at all. For that case (and another similar one) switching to RDS MariaDB worked out. It turned to be 2-3 times faster than Aurora Mysql with same instance class. Could you comment?

[@doitintl]

Thanks for watching the episode + glad to hear you liked the content :). Now to answer your question (via Kate from the episode): "MySQL is in general a single-threaded database designed for high volumes of queries as opposed to large analytic or data warehouse type queries. MariaDB and MySQL are optimized for different types of workloads. Something that works well in one may not work well in the other. MySQL tends to excel at complex joins and sub-queries whereas MariaDB is often better at recursive CTEs and analytics. If you wished to stay using MySQL rather than MariaDB, then you can look at parallel query on RDS Aurora MySQL. This allows you to run complex queries directly against the storage layer in a parallel fashion. docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-mysql-parallel-query.html"

[@baligo3760]

@@doitintl Thank you, perhaps we will give it a try

[@srinivassripathy1439]

For any DBA , application team would be the first customer. He should be there in this IT ecosystem.