Differences in key database design and architecture
Date: Mon, 15 Jan 2024 00:47:33 +0530
Message-ID: <CAEzWdqfaNDg=x5LbbBCqT5HRbST_MN=DX2UMd+t1zhxDtYJOag_at_mail.gmail.com>
Hello Listers,
We have mainly worked in on-premise database world and that too in "Oracle database" and we are well versed with underlying Oracle database architecture and its optimizers working and designed and application development on top of this.
Now that organization is choosing AWS cloud as target state and thus the databases we are exploring for some new development project are mainly AWS aurora postgresql and mysql. So wanted to understand, if there is any key design/architectural changes should the app development team or the database design team, should really aware about, so as to take right decision on any new development project or in case of moving an existing Oracle database system to AWS postgresql/mysql databases?
Is there any list of differences(as compared to Oracle database) in key concepts like for example basic design concepts, Normalization, Partitioning, clustering, backup and recovery, Indexing strategy, isolation level, performance which one should definitely be aware of?
I agree, It may not be the right forum for this one but I am trying to check if anybody has gone through a similar path being worked on Oracle database for majority of the career span.
Regards
Yudhi
-- http://www.freelists.org/webpage/oracle-lReceived on Sun Jan 14 2024 - 20:17:33 CET