Below you can see how that works schematically.īig promises from Oracle about MySQL HeatWave on AWSīy making MySQL HeatWave on AWS available, Oracle has created an option to do transactional workloads, analytics and machine learning within AWS in a single database. At the end, HeatWave merges the partitions back together. Data is first divided into partitions, which are then processed in parallel. Those are the two prerequisites for providing both excellent performance and scalability. MySQL HeatWave is massively parallel and massively partitioned. As such, today’s announcement is quite a big deal. However, Oracle has been working on MySQL HeatWave for more than a decade.
If MySQL HeatWave does what it promises, you don’t have to do that anymore.Īdding a query accelerator to a transactional MySQL database may not sound that complicated. And thus have to migrate a lot of data between databases. Hence, for things like best performance and scalability, users often use multiple databases side by side. It is also part of the MySQL database, which was originally designed for transactional purposes, not necessarily for the highest performance in terms of the queries themselves. As that term suggests, the goal of HeatWave is to make MySQL queries run faster. HeatWave is a so-called query accelerator. We reproduce part of our explanation from that article below for convenience. You can of course read that article again by clicking here. In it, we also explained what HeatWave actually is. A quick refresher: what is MySQL HeatWave again?Įarlier this year, we wrote an article about the addition of Machine Learning to MySQL HeatWave. That’s why Oracle has taken the step of making MySQL HeatWave available on AWS. In addition, there are simply many customers who use other services from the AWS ecosystem (S3 for example). The cost that AWS charges to move data from their environment elsewhere is quite high. In the case of HeatWave, Oracle would no doubt much prefer that customers purchase this query accelerator within OCI. In an ideal world for Oracle, it wouldn’t have to make announcements like the one today and, earlier, the one around Interconnect for Azure. That is, Oracle’s Larry Ellison usually has some remarks about AWS at Oracle events, to which AWS then responds (usually without specifically naming Oracle as the recipients of the comment). That’s a bit more controversial, of course, because Oracle and AWS are not the best of friends. Only now it’s not about Microsoft Azure, but about AWS. You can see today’s announcement as a similar step. This makes it possible to run Oracle databases without leaving the Azure environment. We recently saw an example of this with the expansion of Interconnect for Azure with the Database Service for Azure. In addition to regular updates to its own OCI environment, Oracle has also clearly set itself the goal of offering Oracle services on other public clouds.
MySQL HeatWave on AWS is intended to provide a native experience for AWS customers and promises much better performance than AWS’ own offerings, at a significantly lower cost.
0 kommentar(er)
