- Le plus récent
- Le plus de votes
- La plupart des commentaires
As you are building this solution on Amazon Aurora, the first thing is to be aware of the benefits and limitation on Aurora platform. The best place to look is here. Mainly you should look at the Max volume size for Aurora MySQL cluster (128 TiB) and Max SQL table size (64 Tib).
One great resource that I highly recommend too look at is the Oracle to Aurora MySQL Migration Playbook that potentially will provide a lot of answers to your questions. Even though if you are not really migrating (you are redesigning) the hints and points to consider in this resource are valuable.
One thing else to consider is to understand how Aurora is working. Amazon Aurora provides a powerful approach on running RDBMS engines. The versions of DB's running on Aurora are modified to benefit from Aurora architecture but they are mostly drop-in compatible with what you might know from MySQL. In brief, Aurora decouples storage from the DB compute resource and some of the operations are pushed to storage layer and it is not done in the server node layer. This provides a huge performance benefit.
I highly recommend that you get acquainted as well with how Aurora works. I recommend watching this video from re:Invent 2022 that explains the inner workings in less than one hour.
At last, you can look at the best practices for Aurora MySQL that you can use as input in your design.
Contenus pertinents
- demandé il y a 2 mois
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 4 ans
- AWS OFFICIELA mis à jour il y a 3 ans
Thank You So much for the details. I went through few of them, and it seem there doesn't exist any specific issues though apart from the database size and table size restrictions.
However, going through some blogs, I saw mysql has some specific designs with regards to its indexes as compared to others. In mysql the indexed are clustered indexes which mean the rows are embedded inside the b-tree structure of the primary key. While non clustered cases the rows are stored separately from the indexes. So many secondary indexes access may be terrible idea here. Also saw few discussions on the isolation levels, using UUID as primary keys etc. Not able to digest fully the exact pros and cons though.
So, wanted to understand if we have any such list of points, which we need to be aware of before doing table design or application design on Aurora mysql or postgress?