Join Lois Houston and Nikita Abraham, along with Alex Bouchereau, as they talk about Oracle Maximum Availability Architecture, which provides architecture, configuration, and lifecycle best practices for Oracle Databases.   Oracle MyLearn: https://mylearn.oracle.com/ Oracle University Learning Community: https://education.oracle.com/ou-community LinkedIn: https://www.linkedin.com/showcase/oracle-university/ Twitter: https://twitter.com/Oracle_Edu   Special thanks to Arijit Ghosh, David Wright, Ranbir Singh, and the OU Studio Team for helping us create this episode.   --------------------------------------------------------   Episode Transcript:   00;00;00;00 - 00;00;39;11 Welcome to the Oracle University Podcast, the first stop on your cloud journey. During this series of informative podcasts, we'll bring you foundational training on the most popular Oracle technologies. Let's get started. Hello and welcome to the Oracle University Podcast. I'm Nikita Abraham, Principal Technical Editor with Oracle University, and I'm joined by Lois Houston, Director of Product Innovation and Go to Market Programs.   00;00;39;18 - 00;01;12;09 Hi, everyone. Last week, we discussed Oracle's Maximum Security Architecture, and today, we're moving on to Oracle Cloud Infrastructure's Maximum Availability Architecture. To take us through this, we're once again joined by Oracle Database Specialist Alex Bouchereau. Welcome, Alex. We're so happy you're becoming a regular on our podcast. So, to start, what is OCI Maximum Availability Architecture? Now, before we actually jump into the specifics, it's important to understand the problem we're trying to address.   00;01;12;11 - 00;01;38;01 And that is database downtime and data protection. We don't want any data loss and the impact of both of these types of occurrences can be significant. Now, $350K on average of costs of downtime per hour, 87 hours average amount of downtime per year is pretty significant. So, it's a very, very common occurrence. It's $10 million for a single outage, depending on how critical the application is.   00;01;38;03 - 00;02;02;28 And 91% of companies have experienced unplanned data center outages, which means this occurs fairly often. So, what can we do about this? How do we address the problem of data loss? It's important to understand a different terminology first. So, we'll start with high availability. High availability provides redundant components to go ahead and ensure your service is uninterrupted in case of a type of hardware failure.   00;02;03;01 - 00;02;24;24 So, if one server goes down, the other servers will be up. Ideally, you'll have a cluster to go ahead and provide that level of redundancy. And then we talk about scalability. Depending upon the workload, you want to ensure that you still have your performance. So, as your application becomes more popular and more end users go ahead and join it, the workload increases.   00;02;24;26 - 00;02;42;28 So, you want to ensure that the performance is not impacted at all. So, if we want to go ahead and minimize the time of our planned maintenance, which happens more often and a lot more often than unplanned outages, we need to do so in a rolling fashion. And that's where rolling upgrades, rolling patches, and all these types of features come into play.   00;02;42;29 - 00;03;10;20 Okay, so just to recap, the key terms you spoke about were high availability, which is if one server goes down, others will be up, scalability, which is even if the workload increases, performance isn’t impacted, and rolling updates, which is managing planned updates seamlessly with no downtime. Great. What's next? Disaster recovery. So, we move from high availability to disaster recovery, protecting us from a complete site outage.   00;03;10;27 - 00;03;35;02 So, if the site goes down entirely, we want to have a redundant site to be able to failover to. That's where disaster recovery comes into play. And then how do we measure downtime and data