 So, I have a ton of, I have quite a few slides and I'm going to try and run through these as quickly as I can. Starting first with reintroducing all of you to MySQL, you know, the product has been around for some time. It's been there for about 25 years. And for those of you that are not really familiar, there's this company called database engines.com, which monitors about 350 databases across the world, ranks them in order of their popularity. They use different parameters, they look at job boards, they look at technical discussions and they create a list of people's database popularity. Now MySQL has been the most popular open source database on that list, at least for the last five years that I've been here. In fact, and a couple of years ago, it was also awarded the database of the year, which was an extremely proud moment for us. The reason we are able to kind of maintain this lead is because it's also popular with developers. If you look at surveys done to measure engagement with the developer community, whether they are from Stack Overflow or JetBrains, MySQL remains a very popular database amongst the entire open source, you know, crop of databases out there. And all the work that these developers do, it finally results in the fact that there are a lot of innovative organizations out there that are running across, running on MySQL. MySQL is the database behind Facebook. Facebook, as we know, has three billion users, lots of queries, lots of interactions with the database. It's used in social applications like Twitter, it's used in Pinterest, and then on e-commerce side, it's the main transactional database for Booking.com, which is booking almost one and a half million room nights a day. So massive, massive scalability, massive use case. MySQL is also the database behind the e-commerce applications of Netflix and Uber. So, I guess what I'm trying to say is that, you know, it's even though very light and very easy to use database, it has been used at scale in applications, in industries across different countries. We see a lot of use cases in finance recently because, you know, with the pandemic, one of the things that happened was everything went digital including currency, a lot of countries are launching digital currency now, a lot of payment processing applications are coming up, super apps are coming up, and we see old traditional banks pivoting to these new use cases, and we have a bunch of customers in that area that use MySQL. Old school manufacturing companies are also using MySQL to run their IoT applications, and especially in this part of the world, we've seen a lot of use cases deployed by government. We've got a lot of support from government, government to use open source in providing citizen services, you know, to their population. So a bunch of different Open Source applications are running on MySQL, and the common use cases that we've seen are, you know, content management, digital payments, authentication systems, and this list has continued to grow. MySQL is one of the fastest growing businesses inside Oracle globally, and we're really overwhelmed by the number of users that use our product. We see almost about 100,000 downloads of MySQL on a daily basis from MySQL.com, and what this has really done is it has prompted us to kind of like look back and see how do we provide highly available and secure infrastructure and database architecture to our users because they're building mission critical applications, right? So in the past, database HA from MySQL was a very manual process. We didn't really offer a lot of tools and, you know, for the database engineer to build high available solutions, and there was a lot of customization that the DBA had to do. The DBA had to think about, you know, user management, configuration, replication, etc. And everything was unique to that particular installation, which also makes it very hard to support because then, you know, there's just a small handful number of people who know what's going on inside. Now what we've done is we've come up with something called InnoDB cluster, and InnoDB cluster typically has three, at least three nodes, one primary and two secondaries. And when one of the nodes fails, the other one automatically takes over, and HA is natively built into the InnoDB cluster, so all tasks for high availability are done automatically. You can also have one cluster in one region, and then connect it to a second cluster in a different region through asynchronous replication. And that basically allows you to provide a disaster recovery scenario so that if an entire region goes down, you can do a manual failover and move to the other region. There are going to be, sorry, suddenly I've become very loud, there are going to be a lot of, there are five more sessions around MySQL aspects such as InnoDB cluster later on during these three days, and I would encourage you to attend those sessions by my more technical colleagues who can dive deeper into these different technologies. The other thing that the whole world is focused around is on security. Most of data breaches is very high. Data in front of you is from a study done in the US where every data breach is costing a company somewhere around $10 million, and a high number of companies have experienced a data breach. So it's almost like you start to wonder, is it a question of if, or is it a question of when I will have a data breach, right? So we have to be prepared around that. And then this is a minor plug into linking back with open source software as well. Red Hat does an annual survey around the state of open source in the enterprise, and when they first started doing the survey about four years ago, the number one reason why companies or CIOs were looking at open source was totally cost of ownership. It's going to help me lower my bill. Today that situation has changed where the top two reasons are better security and higher quality software as the two main reasons for that. In fact, 89% of enterprise CIOs surveyed by Red Hat actually believe that open source software is of better quality than proprietary software because people are able to look at the code. The code is auditable. Open source companies have also done a tremendous job of providing bug fixes and patches in a timely manner, and in the last four, five years, the acceptability of open source in the enterprise has really increased. On the same lines, MySQL has another version that we call as the enterprise version. That's our paid version. We love all MySQL users, whether you're using our free version or our paid version, but the paid version does come with a lot of additional features and functionality, especially around security that is built into the product. You don't have to look at other tools to try and make a really secure solution. I've listed down a few of the features, and then you can find out more about this on the web, but basically all the key things like transparent data encryption, MySQL audit, firewall, enterprise masking, a single pane of glass to monitor your entire MySQL estate, all that stuff is available through the MySQL enterprise edition at a very small nominal cost compared to commercial editions of other database software. One other area that we have been focused around is to maintain our popularity with developers and focused on how to make developers make it easy for developers to work with MySQL. We've been consistently receiving feedback that MySQL, you're doing too many updates. You have a lot of new versions coming up, whereas I've got production environments running on MySQL, and I can't keep doing updates and patches on a regular basis. So right now, our current version is 8.0.31. The next MySQL release that we have will be what we are going to call as a long term support release. And that product will have regular bug fixes and patches, but it will be supported for a minimum number of eight years, three years on extended support and five years on premier support. So if you're running an environment where you want complete control, you want complete visibility on and not have to do regular changes and you don't have to cope with the patch update madness on a regular basis, you can pick the long term support release as your product. And if you're the kind of customer who wants to look at the latest and the greatest update and be able to have the latest innovation, we're also going to have innovation releases. We're going to make it easy to migrate between the LTS release and the innovation release, but you can pick and choose what you want, which world do you want to live in. That I think will hopefully give developers the confidence to continue building their applications on MySQL. And then finally, we've also created this marriage between the most popular open source database, which is MySQL and the most popular development environment, which is Visual Studio. And we put all features of MySQL shell in Visual Studio code so you can get everything that MySQL shell does to manage and configure your database, but with GUI now that we have MySQL shell for VS code. And then finally, we also added the rest service architecture. So you can talk to your MySQL database through the MySQL router. It's supported on OpenAuth 2, provides low level security, great way to serve up JSON documents. A lot of innovation actually, there was a MySQL summit back in Redwood Shores just two weeks ago. So we have had so much innovation and I really encourage all of you to come to the different MySQL sessions tomorrow. We also created a launch and open, launch and operator for Kubernetes. This product is developed by the same team that builds the InnoDB cluster. And it's currently a level three operator, but it has, it automates all the major tasks of deploying InnoDB cluster in a Kubernetes environment. Our hope and our, not our hope, our long term goal is to continue to develop the operator and move it to a level four operator, which will have, you know, provide more insight around alerts, around logs, et cetera. So watch out for this space. And I think one of our other sessions tomorrow is about using the operator in a Kubernetes environment as well. Moving on, all the stuff that I've spoken about is so far is stuff that we have been doing on premise. And if you're following cloud databases, MySQL has had some really great innovation with a product called MySQL HeatWave, which has attracted a lot of press attention over the last few, you know, few quarters. So MySQL HeatWave cloud service is a service that's available on Oracle cloud infrastructure. It's a hundred percent managed service. So whatever typically a DBA does, we do it for you so that the DBA can, you know, focus their attention on the, on the application side of the house and all regular OS patching, network management, et cetera is done by the service in an automated manner. The HeatWave cloud MySQL HeatWave is what we are calling a single database for OLTP, OLAP, and ML. As we said earlier in this, earlier in this talk, right, and we showed you that MySQL is extremely popular with social applications, e-commerce applications. I imagine you have an e-commerce application connected to MySQL HeatWave, which is, as I mentioned, a single database for OLTP and OLAP. Because of inbuilt machine learning, that your customer who's out looking to buy something on your e-commerce application will get real-time recommendations on other products that they can buy. Because again, it's a single database, you can run analytics without ever having to move data out of your transactional environment, putting it into, you know, single-purpose analytics database. So there's no ETL required at all. HeatWave works with the standard machine learning tools that AI enthusiasts are familiar with. It also works with visualization tools like Oracle Analytics Cloud, Tableau, et cetera. So one single place to do everything. If you built your transactional workloads on MySQL, this is a really good solution for you and you don't have to think about any ETL activity to work on MySQL transactional business anymore. On a high availability standpoint, on the cloud, deploying a HA cluster is very simple. When you open the OCI console and you're trying to provision, you know, creating your DB systems, you just choose the, you know, hey, I want a HA cluster and the system will kind of create those clusters for you. So it's as simple as that. And if you're wondering how does this product compare from a pricing standpoint with everything else that our competitors have, we ran some standard TPCH queries on a benchmark and found that it's way faster than AWS Aurora and because it's faster and is already priced cheaper, customers can actually save a bunch of money. So that's with Aurora and this is with Snowflake, which is, you know, a purpose built analytics database. We show a lot of price leadership there as well. And then initially when we launched with HeatWave, we just had one particular, you know, shape available. Now we're announcing more shapes available on the basis of customer demand, adding more capability to improve price performance, adding more data handled per node as well, all the while, while, you know, continuing to demonstrate price leadership. Now switching gears and talking a little bit about automation that, you know, and what are we doing on that front? So MySQL HeatWave has something called MySQL Autopilot, which is a machine learning powered automation. So when you're starting to, you know, use MySQL HeatWave, it looks at your, it looks at the information that you provided while creating the database system and gives you a recommendation how many nodes you should have, what should be the shape of the node. It looks at your data and figures out how can it load this data quickly in a parallel way in the memory of the HeatWave nodes. And once the advisor has finished creating this system for you, it continues to kind of like monitor in an automated fashion that entire system. If a node fails, it detects that a node has failed. It will automatically provision another node. It will automatically load data on to that other node and, you know, basically automates most of the regular tasks that you would have to do. And after the system is up and running, it continues to monitor it, it continues to check what have you, you know, provisioned for, what is your actual usage looking like, should you be scaling your system up, should you be scaling your system down. So all these facilities are already integrated in the Autopilot. So analysts have been extremely, you know, positive with their praise, praise around MySQL HeatWave. You know, I have some quotes here that from IDC may very well be the single greatest innovation in open source cloud databases in the past 20 years. And I would encourage you folks to go to oracle.com slash MySQL and read some of these, you know, analyst, white paper, so to speak for yourself. We have a lot of customer testimonials there as well. We have a lot of early adopters for HeatWave. And actually not just early adopters, now people are putting production workloads on HeatWave. And we have quite a few case studies out there and I would really encourage you guys to go look at those. At FOSS Asia, we have these five sessions where all the things that I spoke about just in one slide, people are going to spend 50 minutes going deep into them and, you know, kind of like having a deeper discussion with you on that. So I'm really hopeful that, you know, you guys show up tomorrow in large numbers to all these different five sessions and talk to more knowledgeable people than me as to what really makes all these technologies work. And then finally, if you haven't done already, go create a trial account for MySQL HeatWave. There's $300 of free credits. Look at it, play around with it, ask questions on community forums and get started. Thank you.