- Más nuevo
- Más votos
- Más comentarios
Hi, in general, database principles apply in the same form. One architectural choice to make, is whether are you moving the database (the whole data) to the cloud, or are you just replicating it.
Assuming you are moving the database to the cloud, I'd suggest looking into Aurora and RDS. I have a sweet spot for Aurora because it tends to be slightly costier, but it scale globally better, so the choice of Aurora vs plain rds needs to be counted into.
For Aurora migration guide, you can look into this: https://docs.aws.amazon.com/prescriptive-guidance/latest/patterns/migrate-data-from-an-on-premises-oracle-database-to-aurora-postgresql.html.
Best practices for Aurora migration can be looked here: https://pages.awscloud.com/rs/112-TZM-766/images/EV_best-practices-for-migrating-from-oracle-to-amazon-aurora_Jul-2021.pdf
Hi,
Did you specifically envision Aurora Serverless: https://aws.amazon.com/rds/aurora/serverless/
It will relieve from the "undifferentiating heavyweight lifting" (patching, HA, scaling, etc.). So, it means more time to dedicate to your application vs taking care of the infra resources.
You may want this article that will explain why you should migrate as an Oracle shop: https://aws.amazon.com/tutorials/break-free-from-legacy-databases/why-migrate-oracle-to-amazon-aurora/
This article about a success story for a large-scale migration may also interest you: https://aws.amazon.com/blogs/mt/how-tmap-migrated-their-large-oracle-database-to-amazon-aurora-mysql-using-aws-dms/ Full of interesting takeaways.
Didier
Contenido relevante
OFICIAL DE AWSActualizada hace un año- OFICIAL DE AWSActualizada hace 2 años
- OFICIAL DE AWSActualizada hace un año
- OFICIAL DE AWSActualizada hace 7 meses
Thank you. If we forget about migrating existing database for time being, and consider opting for a freshly new aws database (say Aurora postgresql) how the basic design principle would change or differentiated( in regards to indexing, partitioning, isolation , backup recovery etc) considering we only have past experience working in Oracle Database. Is there any document around this?
This blog post describes many of the similarities & differences between Oracle and PostgreSQL, viewing things from an AWS perspective https://aws.amazon.com/blogs/database/challenges-when-migrating-from-oracle-to-postgresql-and-how-to-overcome-them/
Thank you so much.
We saw few articles (one as below) on postgresql database table partitioning which has caused issues when number of partitions in the base table grow's. Also saw multiple discussion where vacuuming becomes an issue in the MVCC type database architecture in postgre. Are these also holds true in aurora postgresql and something to understand properly while designing application in aurora postgresql ? And does anything similar also exists in indexing, clustering concept too, as compared to other databases like oracle?
https://www.kylehailey.com/post/postgres-partition-pains-lockmanager-waits#:~:text=In%20above%20graphs%2C%20our%20production,partitions%20for%20the%20core%20table.