Inside MySQL: Sakila Speaks
The Inside MySQL, Sakila Speaks podcast is dedicated to all things MySQL. We bring you the latest news from the MySQL team, MySQL product updates, and inciteful interviews with members of the MySQL Community. Sit back and enjoy as your hosts, Fred Descamps and Scott Stroz, bring you the latest updates on your favorite open-source database.
info_outline
Let HeatWave Drive: The AutoPilot Advantage
08/21/2025
Let HeatWave Drive: The AutoPilot Advantage
In this episode, leFred and Scott are joined by Onur Korcerber to explore the many features of HeatWave AutoPilot. Learn how AutoPilot’s intelligent automation helps manage MySQL instances with ease, optimizes performance, and reduces operational costs. Onur shares practical insights and real-world examples showing how customers can streamline their database operations with HeatWave AutoPilot. ------------------------------------------------------------- Episode Transcript: 00:00:00:00 - 00:00:31:20 Welcome to Inside MySQL: Sakila Speaks. A podcast dedicated to all things MySQL. We bring you the latest news from the MySQL team, MySQL project updates and insightful interviews with members of the MySQL community. Sit back and enjoy as your hosts bring you the latest updates on your favorite open source database. Let's get started! 00:00:31:22 - 00:01:03:00 Hello and welcome to Sakila Speaks, the podcast dedicated to MySQL. I am leFred and I'm Scott Stroz, joining us today is Onur Kocberber. Onur is currently a director of Development at Oracle, leading efforts on MySQL HeatWave, specifically working on the AutoPilot. Based in Oracle's Zurich office, Onur focuses in advanced research and development to improve cloud database performance through interpretable machine learning techniques. 00:01:03:02 - 00:01:24:16 He plays a key role in the ongoing growth of HeatWave, including work on new offering like the HeatWave Lakehouse and HeatWave GenAI service. Welcome, Onur. Thanks. Thanks leFred, thanks Scott. Great to be here. So Onur, can you tell us a bit about your journey? What led you to Oracle and specifically to the MySQL HeatWave team? All right. 00:01:24:16 - 00:01:53:10 So I, I was a grad student at EPFL Lausanne in Switzerland, and, I was doing research specific doing database, accelerators, both for, with hardware and software. And, at the time, I knew that Oracle Labs had a very exciting project about, building basically hardware, software, core design, database machines. And once I graduated, I knew that there were really good set of people. 00:01:53:10 - 00:02:21:18 And that's, how I joined. So I came to basically Zurich, to to the Oracle Labs branch. And then eventually, maybe fast forward ten years, we have, HeatWave database service, but, what we see includes MySQL and other things I will discuss today. That is fantastic. So, Onur, this entire season has been dedicated to, everything AI. 00:02:21:18 - 00:02:47:07 What AI offerings that HeatWave has and some of our listeners, I would guess maybe many of our listeners probably aren't too familiar with, HeatWave AutoPilot. Can you give us a high altitude overview of what AutoPilot is and, what problems that might be resolved? So the database systems today are all cloud databases, right? And, these are many services. 00:02:47:07 - 00:03:21:04 And the onus is on us, in terms of managing these systems. So the customers are expecting basically a full, full fledged, automated service with no, let's say rough edges. And that's where, AutoPilot, comes into play. And when we started the project, when, MySQL HeatWave was becoming a cloud service, we, also started the AutoPilot project, and, we basically targeted four different, let's say, problem domains. 00:03:21:04 - 00:03:53:04 So these are, setting up the system, data, basically loading the data or data management query execution and then failure handling. And, for each of these, categories, we basically looked at what, how we could, improve customer experience as well as customer performance. And at the same time, we put the machine learning, as one of our, basically main objectives because, this is a very old topic, right? 00:03:53:04 - 00:04:18:12 This is this is not a new topic like database management on automatic database, admins and DBAs and such. So that's why we took all the, academic research, plus the realities all today, which is the cloud services. And then, we looked at these four different pillars and then fast forward to today, we have like a double digit numbers in the AutoPilot suite. 00:04:18:14 - 00:04:55:12 Wonderful. And that's awesome. So and why then, this HeatWave AutoPilot is a game changer for users. Right. So, one of the things that we were seeing in the early days of our services that customers would sometimes put together, let's say, scripts or rules or let's say, some sort of, business practices, right? And in AutoPilot, we are taking all of those, especially what you're observing or what you're anticipating, right, that, the customers will have problems with. 00:04:55:16 - 00:05:18:07 And then we are offering them out-of-the-box ready to use for the for the customers. Some of those are fully automated, like, let's say, for or planned improvements. These are like these are happening completely transparent to the use it and some of the features that are a bit more about, the cost optimization of the service or performance optimizations are provided as an advisor. 00:05:18:08 - 00:05:43:03 So essentially we are constantly watching what the customer might, let's say, what would the cost of problems that the customers might have? And we are offering it out of the box included in the, in the service. And that is something, we see when we look at our competitors, we see that, some of the problems that we are solving are just seen as kind of still left as rough, rough edges. 00:05:43:05 - 00:06:02:08 And that's why it is really important. And at the core of it, we have a lot of machine learning models. These models are automatically up to...updated as we also update the version of the service. Therefore customers don't have to worry anything about, basically those, those, those problems that they are running into. Great. 00:06:02:08 - 00:06:31:10 Thank you. So, and when I follow what you just said, then, it seems that, these AutoPilot feature can save OCI customers some money, right? Right. So for certain cases, absolutely. For example, let's take auto provisioning. This is the feature that, the, made available almost at the same time when the, with the GA and, since our GA, this has been used, very actively. 00:06:31:10 - 00:06:54:02 And in this feature, for example, we say this is the number of nodes, that's, a customer should provision for accelerating their, analytical queries with HeatWave. And the great thing here is that, they don't have to overprovision their cluster or they don't, they don't need to under provision their cluster and then run into all sorts of possible issues. 00:06:54:04 - 00:07:13:07 So then one, one part of it is that they have the optimal cost, right? So they, they pay or they provision what they, what they should. And at the same time they also say, save time by just not having to, worry about it. And then similarly, for example, we have an auto load and unload feature. 00:07:13:07 - 00:07:40:05 So if you see there is some let's say there is going to be some benefit from from customer workload, we would automatically load or unload tables. And again, this would either give you a performance boost, which again translates into some sort of cost saving, or at the same time we would just, unload the unnecessary tables so that the customer wouldn't have to, let's say, increase their resource consumption, because they don't they don't have to. 00:07:40:07 - 00:08:15:12 And then we have a bunch of other like, similar features actually, that that will do. For example, there's auto compression that already gives you better price performance, but by default. Right. So that's definitely, every the most of the optimizations we do is translating into some sort of cost saving for the customers. That's awesome. I find that actually pretty, interesting that we offer ways to make sure the customer is basically streamlining their process, and then they're not overpaying for resources because some people might spin up a huge instance when they don't, in fact, need it. 00:08:15:14 - 00:08:39:07 So what are some features of AutoPilot that can help make storing and retrieving data a little bit more efficient? So I mean, let me give you an OLTP example. Of course auto indexing is is one of them. Right. So indexing, is definitely one of the holy grail problems in computer science, I would say. And we have a feature, that basically recommend secondary indexes. 00:08:39:07 - 00:09:04:23 So that's I see people ... people who are familiar with the MySQL know that how important indexes are. So we actually have an index advisor and that's, pretty effective. We see this today with customers as well. And that's just working really well. And having the right indexes is definitely making the, data retrieval, extremely efficient. 00:09:05:01 - 00:09:26:21 And if I were to give you an example from the analytical site, we, we have adaptive query execution. So we are basically over time, the improve the, the the query plan. Right. So this is also making, everything, a lot more efficient. And if I were to give maybe an example from the Lakehouse side. 00:09:26:21 - 00:09:57:14 So this is another, basically feature where we deal with semi-structured data. We do we, we automatically ingest, the unstructured files by understanding the, the, the schema. And, this way we can represent the unstructured data in the right format, which could translate into a better, let's say, space, usage guide so that you don't have to maybe pick a larger type than anticipated, than what the customer anticipated. 00:09:57:16 - 00:10:32:13 So and all these things, are they sometimes they look small, but these are the real problems because, especially when it comes to whether it's indexes or whether it is query plans or whether it is unstructured data, in all these instances, we are dealing with hundreds, if not thousands of either queries or tables and such. And and for a particular user, maybe dealing with 1 or 2 is easy, but dealing with thousands, I think every DBA would know or every user would know that it's, it's it's a tedious process with a lot of gotchas. 00:10:32:13 - 00:10:59:09 And corner cases will be basically take all these things into account in our AutoPilot suite. And then we update our, learnings and our optimizations as the versions go. But thank you. Yeah. Nice. Good answer. So what do you think are, the biggest misconception that the developers have about, machine learning driven, database optimization, right. 00:10:59:11 - 00:11:19:18 Because, yeah, there is the old DBA. Is that the they should know everything. And then the also thwy run the reports and sometimes people say, yeah, is it good or not I don't know. So do you know that, do you have an answer for this. Yes. So this is one of my favorite topics. Yeah. 00:11:19:19 - 00:11:52:18 So this is, something that we, we we have an internal discussion going on. Right. So I am also receiving a lot of requests from other teams or, people who are, and like, very, let's say, excited or ambitious about, applying like, machine learning to, to their domain, to their problems, like, one of the things that I keep seeing is that so there is, basically systems for ML and ML for systems that I, this is, I think, a very good, way of describing. 00:11:52:20 - 00:12:22:20 So we are at the end of the day, we are building computer systems and we should use ML for optimizing our computer systems. So and most of the time what I see is that like people who start, like basically trying to people who start trying to, apply ML, they put ML is a first object, whereas it should be actually not the first objective, it should be first the systems, how we build a system, a computer system. 00:12:22:22 - 00:12:46:22 And then we need to understand what is the hole, right, in our problem space that we can fill with machine learning. So most of the people who go and collect, let's say a data set and a the draw, let's say a regressor or a classifier on that data set. They say that it or it works well in the test, but it doesn't work in the in the real like a production like. 00:12:47:00 - 00:13:09:20 And to me this is the missing a systems inside. So we basically have to have a systems inside. So I will give you a very specific example. For HeatWave for when we are loading data into HeatWave, we can control InnoDB parallel thread and you know, parallel, like a thread count is a known lock that, anybody would know, let's say, how to tune. 00:13:09:22 - 00:13:32:01 But when it comes to the HeatWave load, it is, basically like the trigger behavior is changing, right? So basically we need to understand why the thread break here. The idea is changing. So that means that we have to collect the data in a way that we exercise the parts that HeatWave would exercise now. So if people were basically just saying, oh, like machine learning is going to solve everything for us, right? 00:13:32:01 - 00:13:54:09 Then we start with the data set. It will work. Basically, first the system inside, then the machine learning. You will be highly, highly effective. So that is why I think the second part is a while. Sure that what we put a lot of focus on is interpretability or explainability. So we try to fail our models first before the customers fail them. 00:13:54:10 - 00:14:23:06 alright and with that, we this is we just ship models, right. So this is, this is actually very, very important because otherwise it's some people might say, oh, you know, let's just fancy like a version of rule based tuning or it only works in certain cases. Right? So, basically to summarize, there is a lot of technical debt in machine learning models, but using the systems inside you can get good system engineer. 00:14:23:06 - 00:14:42:02 I think it's it's the real, secret sauce of shipping machine learning models that are effective at production. And then it's a long topic that after you ship it, you have to monitor them. You have to make sure that you are not regressing. There are not too heavy concepts and such. So yeah, what I would change that ML is machine learning is a tool. 00:14:42:04 - 00:15:12:07 And like any tool, it has its own drawbacks. And as long as we are aware of them, we can, these can provide really strong systems, that take advantage of ML. But again, systems first, ML second. That is my philosophy. I think that's actually a pretty good philosophy. So I know you might not be able to tell us everything, but are there any up any upcoming features that you're particularly excited about that you can actually talk about? 00:15:12:09 - 00:15:39:17 All right, so, well, I think this is not a surprise about generative AI. Right. So generative AI is, now the, the, the hottest, topic that, we are dealing with and, we, are working actively on generative AI based AutoPilot features, let's say. And one important difference there is that, when I say systems first, right, systems is about numerical data, right? 00:15:39:17 - 00:16:01:09 We deal with numbers that are coming in, let's say cache misses, buffer pool heat ratios, read write ratios right or performance and like all these numbers that they are essentially a time series that are just flowing in. And machine learning is like traditional machine learning is is very good at it or sometimes categorical, like, the data set, right? 00:16:01:11 - 00:16:23:22 When it happens, like should, it should have been this way or another. Right. Those are easy. But what is generative AI now bringing is, being able to deal with completely unstructured data. So what is unstructured data is text. For example the text. Then what text means means generating SQL code or text means dealing with logs, right. 00:16:23:22 - 00:16:53:15 Or log files or or automatically, thinking into, let's say like, your own, let's say diagnosis. That goes to data insight. So those are the areas, let's say that, that we are working on. Excellent. So because you're talking about, AI, GenAI, the resources is something, we hear, more and more in the database, area. 00:16:53:16 - 00:17:21:12 So, because HeatWave AutoPilot brings us, already a lot of, intelligence, automation but, what about the the natural language to a SQL. So the NL to SQL, do you think, this will be also something that, will come, for us and, and do you see it as a serious productivity tool for the analyst and the developers? 00:17:21:14 - 00:17:52:18 Are there still, orders, to making it available and, enough, for a production use? Right. That's a very good question. Okay. This is definitely a very hot topic for for everyone in the industry, I believe. And, so, yeah. So what is really happening in the NL to SQL domain is, as the large language models are getting larger, we are seeing a very big improvement in the accuracy of these tools. 00:17:52:20 - 00:18:36:02 And of course, what I mean, my accuracy of the known benchmarks. Right. And also what is really... Another interesting trend that is happening is that, you know, you look at traditional, like benchmarks, like for OLTP, OLAP, you know, TPC-C, TPC-H, TPD-DS right? They've been around for a very long time. What is interesting about, this NL to SQL benchmarks is that the more that they're out, it's, it takes maybe a year or less than a year to, to to get really good scores, you know, like, people are conquering is benchmarks and they're very fast, pace so it is true that it was not ready, but now we are seeing 00:18:36:02 - 00:18:58:06 signs that it is actually, they are getting very, very good at it. And and of course, it really depends on your, your complexity, how many SQL constructs you have. Right. And how complex, it could become because you certain SQL is just pages. Right. So that that means you need an assistant. But certain SQL is just, you know, you just want to learn something about your database. 00:18:58:08 - 00:19:17:02 Maybe you're a business executive or maybe you're a data analyst who is not very well versed in SQL. I can tell good for for for those type of use cases where you're a business analyst or whether you're a data analyst, I think that the tools are definitely there. So more complicated queries where even humans don't write in one go, right? 00:19:17:02 - 00:19:41:15 Like its an NL to query it it's pages right there. It's a great system, but it is performing maybe similar to the coding assistance that that we have todat. But yeah, it's it's definitely in a corner like, it like is is basically something that everybody is looking at actively and so, so we are so that's, I think you will hear, 00:19:41:15 - 00:20:04:08 Hopefully, some more cool news about it, soon.. That's awesome. That's actually something I'm really interested in. Just because, like you said, allowing people to query data without actually having the SQL knowledge is, is kind of intriguing. So one last question. As you, as would the three of us should know. You know, here at Oracle, we tend to eat our own dog food. 00:20:04:10 - 00:20:33:12 And it helped improve MySQL in some areas like high availability where we tuned group replication. Do you have a similar experience with the AI related tools that you could, talk about? Oh, yes. That's a very good, question. And this is an active topic that is, basically, happening right now, within the MySQL Org. So, yeah, I'm working on two different projects. 00:20:33:17 - 00:20:59:02 One is, we are using generative AI, our own generative AI service. I think they've generative AI service to generate, HeatWave release notes. So if you go to mysql.com today and if you look for HeatWave release nodes, you will see that there is actually banner up there that says these nodes are generated with the assistant off assistance of, HeatWave generative AI service. 00:20:59:04 - 00:21:20:12 And this is a system that we built in, again, purely running on our, software. And, it's working. Our technical writers love it. And we have actually working on several other improvements that we we are trying to write more, with that. And it is going to come. So there's...
/episode/index/show/d0cd255f-ccaf-4b55-a7da-5825f8230161/id/37641085
info_outline
HeatWave Hot Takes: The Power of ML and GenAI
08/07/2025
HeatWave Hot Takes: The Power of ML and GenAI
In this episode, leFred and Scott welcome Jayant Sharma and Sanjay Jinturkar to the Sakila Studio for an insightful conversation on machine learning and generative AI within HeatWave. Discover how these cutting-edge technologies are integrated, what makes HeatWave unique, and how organizations can leverage its capabilities to unlock new possibilities in data and AI. Tune in for practical insights, real-world use cases, and a closer look at the future of analytics. ------------------------------------------------------------ Episode Transcript: 00:00:00:00 - 00:00:32:01 Welcome to Inside MySQL: Sakila Speaks. A podcast dedicated to all things MySQL. We bring you the latest news from the MySQL team, MySQL project updates and insightful interviews with members of the MySQL community. Sit back and enjoy as your hosts bring you the latest updates on your favorite open source database. Let's get started! 00:00:32:03 - 00:00:54:17 Hello and welcome to Sakila Speaks, the podcast dedicated to MySQL. I am leFred and I'm Scott Stroz. Today for the second episode of season three dedicated on AI. I am pleased to welcome Sanjay Jinturkar. Sorry if I pronounce it badly. No, you did it right. Hi there. Thank you. So Sanjay is the senior director at Oracle based in New Jersey. 00:00:54:19 - 00:01:21:13 He leads product development for it with AutoML and GenAI with a strong focus on integrating these technologies directly into each HeatWave database. And Sanjay has been instrumental in enhancing HeatWave's machine learning and GenAI tool sets, enabling use case like predictive maintenance, fraud detection and intelligent dicument and Q&A. And also we have a second guest today. 00:01:21:13 - 00:01:48:21 It's a Jayant Sharma. Hi, Jayant. Hello. So Jayant Sharma is senior director of product management at Oracle. He has over 20 years of experience in databases, spatial analytics and application development. He's currently focused on the product strategy and design of the Heatwave MySQL managed services offering. Hey Fred. Thank you, both of you for joining us today. So I'm going to dive right in with the question for Jayant. 00:01:48:23 - 00:02:12:14 Why did Oracle decide to integrate machine learning in generative AI capabilities directly into HeatWave? Thank you Scott, first for this opportunity. And yes, we have to start with first, you know, talking about MySQL, right? MySQL is the world's most popular open source database. And what do all of these customers, the thousands of customers that they have, do with it? 00:02:12:16 - 00:02:47:05 They manage a business process. They manage their enterprise, right? Their focus is on what they want to do, why they want to do it, and not so much the how. That's what MySQL makes it easier. And Heatwave is a managed service on MySQL. Okay, so as folks are modernizing their applications, taking advantage of new technology, they want to be able to use new workloads, new analytics, and modernize their business processes, make it more efficient, make it more effective. 00:02:47:07 - 00:03:09:17 In order to do that, they want to do things such as machine learning and use the benefits of generative AI. However, what they want to focus on, as we said, is what they want, why they want to do it and not the how. So they don't want to have to think about. I have all of this data that's potentially a goldmine. 00:03:09:19 - 00:03:40:07 How do I extract nuggets from it, and how do I safely move it and transfer in between the best of breed tools? I want to be able to do things where they are. I want to bring the capabilities, these new capabilities to my data. I don't want to take my data to where those capabilities are exposed, right? That is why we made it possible to do machine learning and GenAI where your gold mine is, where your data is in MySQL in Heatwave. 00:03:40:09 - 00:04:06:07 Awesome. Thank you. So, I would like to ask you to Sanjay, then. How Do the the, machine learning engine in the HeatWave, offer differ from, using external machine learning pipelines with the with the data we have in the database? It differs in a couple of weeks, specifically how the models are built, who builds them and where they are built. 00:04:06:09 - 00:04:46:09 So our pipeline, we provide, automated pipeline, which can take your data in MySQL database or Lakehouse, and then automatically generate the model for you. So it does the, usual tasks of pre-processing, hyperparameter optimization, and, data cleansing, etc. automatically so that the user doesn't have to do that. We would even go ahead and do, explanations for you in certain use cases, given that this is automated, a big side effect of that is users don't need to be experts in machine learning. 00:04:46:11 - 00:05:16:08 What they need to focus on is their business problem, and how that business problem maps onto one of the features that we provide. From there onwards, the pipeline takes over and generates the models for it. And the third piece is that all of this work is done within HeatWave. We don't take the data going back to what Jayant was say, saying, we have got machine learning and generative AI to where the data resides, not the other way around. 00:05:16:10 - 00:05:47:20 So we are building the models inside Heatwave whereby the data is not taken out and thereby it is more secure and the user does not have to worry about data leakage or track where all they have taken the data and how many times they have done it. So these are the three key ways in which we differ. If you use one of the third party solutions, they will end up asking you to do this on your own or asking you to take the data out of the database and build it on your machine, so on and so forth. 00:05:47:22 - 00:06:21:06 But we have made it automated, easy to use and very secure to do so. So Sanjay, we're going to stay with you to, to keep talking about AutoML in HeatWave. So what are some of the key features of AutoML and how does it simplify model training and deployment for users? Fantastic question. You know, as I said in my in the previous, conversation, we are hitting the common tasks that are associated with model training and deployment. 00:06:21:08 - 00:06:46:03 So let's take training here. Typically when the user has to train a model, they are going to take their data. They will clean it up, do some pre-processing. Then they will figure out which particular algorithm they should be using. Tune those algorithms in doing the hyperparameter tuning, so on and so forth. All of these are individual tasks. 00:06:46:05 - 00:07:12:15 Our goal is to have the user focus on their business problem and take away the engineering piece of it, take away the technology piece of it, and do it automatically for them. So we have this pipeline which does this, all of it, all of it automatically in a single pass. So it will do pre-processing. It's going to figure out, the appropriate algorithm to use during model building. 00:07:12:17 - 00:07:39:05 It will figure out what are the best set of hyperparameters and what their values should be, during the training process and give you the, the model. So that's one part the second part is we provide an ability to deploy these models via REST interfaces. So once the model is trained they can deploy this. 00:07:39:07 - 00:08:09:09 And thirdly from time to time the users data is going to drift. Or what I mean by that is the train model. The data on which it was trained no longer reflects the reality. And in that case, you have to retrain the model. So we provide tools to measure that drift. And if it goes beyond a certain threshold, then you can go ahead and retrain your model automatically. 00:08:09:11 - 00:08:53:01 So these are a couple of ways in which we have simplified the model training and the deployment for users. Thank you. Thank you very much for this, detailed, answer. And now... So as we discussed about, you know, the, the data not leaving, to a third party, product. But I would like to, to ask, to, Jayant, if, if there were some performance improvement that, users have seen by doing this, ML natively in HeatWave, instead of removing the data, to external platforms. Certainly, Fred. 00:08:53:03 - 00:09:24:01 So there are two aspects to this. There's, there are efficiencies that, result and there are performance improvement because of the way AutoML is implemented and how it works in HeatWave. Let's start with the efficiency first. The first thing as Sanjay was talking about right, is that we've automated the pipeline. You have to only focus on what is your business problem and how that maps to a particular task in machine learning. 00:09:24:01 - 00:09:47:04 So for example, do I want to predict something. And therefore use regression, do I want to identify or label something and therefore use classification. And AutoML will figure out which particular algorithm. There are multiple ways in which you may do regression, for example, which particular one applies or is best suited for the task at hand. Right. 00:09:47:04 - 00:10:15:06 So efficiency there is AutoML handles it in a single pass, not the normal process requires you to have an iterative do things multiple times. Try it on multiple algorithms or different ways of solving the same problem, and then evaluate which one does it best. AutoML does this in a single pass by. Very smart ways of sampling your data and running quick tests to identify the best approach. 00:10:15:08 - 00:10:35:15 So that's the efficiency. The second when it does this, why is it so fast? It's so fast because it uses it the full capability of the underlying infrastructure, which is the HeatWave nodes. Right. The number of heat wave nodes you've got the size of these HeatWave nodes. It does these things in parallel and fully utilizes the infrastructure. 00:10:35:17 - 00:11:02:22 So what is the benefit of that? You can do things a) faster and b) potentially cheaper, which gives you the luxury of trying multiple what if scenarios. Right. It's not a laborious process. It's more efficient. So if you know exactly what you want, you get it done faster. If you want to try multiple scenarios, you can do that faster and at a lower cost. 00:11:03:00 - 00:11:32:23 So that is the efficiency and the performance enhancements that you get. Awesome. So all right let's switch gears a little bit GenAI is one of the latest additions to HeatWave. What specific GenAI features are currently available or if you can talk about them in development? So, Scott, indeed. GenAI has been one of the latest additions to our platform and frankly it encompasses two separate components. 00:11:33:01 - 00:12:04:05 One is the customer usage part and the second is the technology part. So from a customer usage perspective, what people want to do is bring in their knowledge bases. And by that I mean bring in the PDF documents, PowerPoint documents, so on and so forth, and ask questions of that or get summaries of that text, or translate that text into another language, or develop a chatbot around it so that they can get answers, things of that nature. 00:12:04:07 - 00:12:36:19 So what we have done is keeping this in mind for an enterprise setting. We have developed the technology components which are needed to serve these needs, such that going back to the earlier conversation, they focus on their business needs, and we provide them the tools to actually, serve those or we provide the plumbing to do so. So what we have done is to provide a full pipeline to ingest their documents and create the knowledge base. 00:12:36:19 - 00:13:04:06 And by that I mean bring in your PDF documents, which will get converted into embeddings and stored into vector store. So we provide all of that. And then we provide ways in which to search this knowledge base and give answers to the users via easy to use APIs like retrieval augmented generation (RAG), or doing just semantic search over those documents or doing summarization or translation. 00:13:04:08 - 00:13:32:14 We also have the ability to, support chat. Now, one very interesting thing that we have done is to provide the users a LLMs, which ran on commodity hardware. Jayant was talking about running this on HeatWave nodes. So we, we, we have provided these LLMs which found on commodity hardware so that people can quickly prototype their application to test it out. 00:13:32:16 - 00:14:00:13 And if they like the results of the like the performance, they stick with it. Or if they want high performance, and then they go to our OCI GenAI services and use those LLMs. So, quick prototyping, quick testing, quick evaluation done using the commodity LLMs commodity, the LLMs which are running on commodity hardware. And then they can use the OCI GenAI LLMs to get high performance. 00:14:00:15 - 00:14:26:07 Now going to your question about what newer things are coming in. You know, OCI is at the forefront of this revolution. And they are providing, newer models, newer frameworks and tools. And we are continuously incorporating MySQL and Heatwave with, their tools and technologies so that we can provide the same to our customers, in coming weeks and months. 00:14:26:08 - 00:14:53:23 Yeah. And then an example would be the agent framework. Right. Integrating with the agent framework, integrating with the hosted frontier models on GPU infrastructure. So you develop your prototype, develop, you can choose to deploy. The integration is preexisting. You don't it's not an after the fact exercise. You use the same infrastructure. And we provide the pre-built integration with those AI services. 00:14:54:01 - 00:15:28:22 Excellent. So because you are talking about, using, these, LLMs, on commodity hardware, which model, are available from these LLMs and how are we using them? So, we provide as I mentioned earlier, we provide two sets of, access to two sets pof LLMs. One are the smaller parameters LLMs, which are running on, commodity hardware on the same cluster on which HeatWave is run. 00:15:29:00 - 00:16:00:12 And in that context, we provide models like, mistral 8 billion or, llama 3 billion, 1 billion. And we are continually sort of upgrading these as newer models come into play, since this is a very fast moving fleet. Also, once people have prototyped it, once people have gotten to see the results, if they want to switch over to OCI GenAI LLMs, then we provide access to the wide variety of LLMs that OCI provides. 00:16:00:14 - 00:16:31:11 Those includes, you know, things like all the llama models, the upcoming models from all the other vendors, all of that is going to be accessible through, all of that is accessible through, MySQL. And these can be used for, as I said, but I do have use cases, be it retrieval augmented generation, chat bots, summarization, translation and many other use cases that, you know, customers continue to think of. 00:16:31:11 - 00:16:57:06 And we are always amazed at the way they are using, this technology. So when we talked to Matt Quinn, in our first episode, he had mentioned, he briefly touched on, security and privacy issues when it comes to GenAI or when it comes to AI. And we all know that OCI's, biggest concerns are and always have been, security and privacy. 00:16:57:07 - 00:17:26:12 How is data privacy managed when training models or generating text using GenAI in HeatWave? Thank you for that, Scott. So security and privacy and data privacy are and have always been Oracle's primary concern. Right. It is true for the OCI the infrastructure. And it was built with security in mind. It has been true of Oracle's ever since Oracle since its inception. 00:17:26:14 - 00:18:04:09 So that is core that is our DNA including for MySQL and Heatwave. So the two primary ways in which this is a benefit here. Number one, the data doesn't move. Number two when it does have to move, as you said, in the case of text generation etc., we don't use only send the relevant snippets. So Sanjay talked about the fact is that you just the documents and then you create embeddings, which essentially that means is you look at various snippets, the model creates a semantic, you know, captures the semantics of it. 00:18:04:09 - 00:18:33:08 So that you can do a similarity. Right. Do you want to search for, GenAI? You'll also get documents that talk about retrieval augmented generation. Even though you didn't ask about retrieval augmented generation, because the embeddings know that these two things are related. So we extract the relevant content and only that is then sent. For example, if you want to if you're using in database a LLMs nothing is sent anywhere, everything stays in your environment. 00:18:33:09 - 00:18:58:04 If you're using an OCI service, for example, the relevant pieces sent that you get the answer and OCI is built, as you said, with security in mind. So the relevant piece that you sent is discarded after it has answer your question. So once again, your data doesn't leave the ecosystem. It stays within the Oracle infrastructure. Your infrastructure. Great and secure like we want. 00:18:58:06 - 00:19:29:03 Exactly. So thank you very much. No. The tricky question that, we have every time we present, anything new or compelling, at conference and stuff, it's that. And I would like to ask you if you could share, with us, a few compelling customer stories or a real world application of, the, ML engineand GenAI in HeatWave, because it's bice theoretically. 00:19:29:03 - 00:19:47:23 But are people using it? Really? And who are they? If you can say, I know we cannot always share names, but maybe some, are public. So if you can explain us a bit of that would be great. Yeah, Fred, that's a very good question. And indeed, all of this makes sense if customers are using it. 00:19:48:01 - 00:20:31:14 So, yeah, let me share a couple of them. In fact, let me share two of them, one on GenAI and one on, AutoML, so on GenAI. And this is a public reference. We have a customers, Smarter D their goal, or what they provide is a platform to track the compliance of a company's policy to the guidelines released by various, bodies, for example, DoD. now, in the past, what they have done is to have an auditor, which is going to compare the policy with respect to the guideline and then say if a specific companies are adhering to those guidelines or not, which is kind of 00:20:31:14 - 00:21:04:12 a, manual process, fairly intensive, right? What they did was to start using, Heatwave GenAI and they stored both the policies and the guidelines in HeatWave GenAI's knowledge based. And then using our RAG using our other capabilities, they compared the policy with the guidance automatically. And the results of these are then given to the auditor. 00:21:04:14 - 00:21:28:15 So now what does what does this do. This reduces the amount of time the auditor has to spend comparing the two. Instead, he or she gets a, very short description of what has been done, what has not been done, and whereby they can make a judgment whether it is indeed adhering or not. So it makes the auditor far more efficient compared to earlier. 00:21:28:17 - 00:21:57:04 So that's a that's a use case in the compliance space for HeatWave. GenAI, I, I would give me another example here. I can't, quote the name, but this is in the industrial setting where the customer wants to have early signals of failures of their computer servers. So they are running, large amount of, workloads. 00:21:57:07 - 00:22:39:20 And these workloads generate logs, and those logs sometimes are indicative of failures. So what they do is they use our log anomaly detection, tool models that, they have built actually, and feed their logs continuously to these models. And these models are trained to detect abnormal logs. So when the model notices abnormal logs, it's going to go ahead and give you an early warning of the fact that a particular system is likely to fail. 00:22:39:22 - 00:23:03:14 An example of that would be hey,...
/episode/index/show/d0cd255f-ccaf-4b55-a7da-5825f8230161/id/37641020
info_outline
AI for the Rest of Us: A High-Level Overview
07/25/2025
AI for the Rest of Us: A High-Level Overview
Kick off Season 3 of Inside MySQL: Sakila Speaks as leFred and Scott welcome Matt Quinn for an engaging introduction to the world of Artificial Intelligence. In this episode, we step back from the database and explore what AI really is, how it’s shaping society and technology, and why it matters to anyone in tech today. Whether you’re just curious about AI or eager to understand its key concepts, join us as we break down the basics and set the stage for a season of discovery. ------------------------------------------------------------ Episode Transcript: 00:00:00:00 - 00:00:31:22 Welcome to Inside MySQL: Sakila Speaks. A podcast dedicated to all things MySQL. We bring you the latest news from the MySQL team, MySQL project updates and insightful interviews with members of the MySQL community. Sit back and enjoy as your hosts bring you the latest updates on your favorite open source database. Let's get started! 00:00:32:00 - 00:00:58:22 Hello and welcome to Sakila Speaks, the podcast dedicated to MySQL. I am leFred and I'm Scott Stroz. Join us today. It's Matt Quinn, vice president and head of AI at Orracle. Matt leads how Oracle Cloud Infrastructure's AI services are adopted by customers in EMEA. Matt brings deep expertise in enterprise software strategy and a passion for making AI both powerful and its adoption practical. 00:00:59:00 - 00:01:21:03 Today he is here to help us unpack what GenAI really means for the organizations we work for and buy from, and what it means for developers, data professionals, and MySQL users everywhere. Matt, welcome to Inside MySQL: Sakila Speaks. It's great to have you with us to kick off season three of our podcast. Thank you very much, Fred, Scott, great to be with you. 00:01:21:08 - 00:01:43:21 Looking forward to, to an interesting conversation and getting us going for season three. Awesome. Matt, thanks for being here with us. So right off the bat, when most people hear the term AI, they probably think of chat bots. But that's just one form of AI. Can you help provide us with like a high overview of the different types of AI that exist? 00:01:43:23 - 00:02:15:10 Absolutely. And I think AI and itself is a broad church, right? There's a number of different, kinds of AI. The term actually dates back to the 1950s as a concept for you know, machine thinking. It's had a couple of false dawns over the time when compute and data to train. I wasn't really quite ready for this, but as we got into the 90s and the early noughties, as compute power grew, as storage grew, a confluence of internet accessibility, lots of data becoming available, and then we time fed forward. 00:02:15:12 - 00:02:33:12 We found that organizations could do the fundamentals of what we know of AI today things like machine learning. So learning a trend and a pattern, looking at what happened in the past and do a statistical regression on that to predict some future outcome based on what happened in the past. And we use examples of this today without even knowing it. 00:02:33:12 - 00:02:52:11 You know, is this email that's coming into my email system, is this spam or not spam? Those kind to classifier types of AI have been prevalent for the last ten, 15, 20 years, and we're moving forward to where AI has this more kind of human interaction. It's surfacing and it's suddenly popped into the zeitgeist, for for conversation. 00:02:52:15 - 00:03:14:03 So it has multiple facets. We have machine learning trained something to do, something very specific, show it, something that it's seen before and enable it to predict the future based on what it's learned. But we're starting to see this wave of generative AI do more advanced, more nuanced, more humanlike things, and I think that's a really powerful kind of inflection point that we've seen in the last two, three years. 00:03:14:05 - 00:03:39:02 Thank you. So because in your first, answer, you said you said about the 70s and 90s, but why is I having such a huge moment right now? So what changed since that time? I think that the real inflection point is the the kind of conversational nature of it. You can speak human to it, and it can speak human back to you. 00:03:39:04 - 00:04:01:13 If I think about how compute evolved, you know, it used to be I had to type cryptic commands on the green screen in order to be able to use a computer, which meant the audience of people who could use computer to do something was very limited. In the 80s is the GUI. The graphical user interface kind of emerged suddenly it was a keyboard in a mouse, and the population of people who could interact with the computer was much broader. 00:04:01:15 - 00:04:19:02 Mobile did the same for us, but you still had to learn things. You had to take the human to interact in a way that made sense to the computer. With generative AI, I think what's happened in the last 2 or 3 years is actually the computer is coming to meet the human. Suddenly it's able to interact with us in our language. 00:04:19:07 - 00:04:37:19 I can have a conversation with it. I can ask a question in natural language. Now I might need to engineer my prompts to get the right kind of outcomes to guide it. Actually, the computer understands what I say. It can meet my language and understand that interact with me in a very human way. And I think that's caught the imagination of people. 00:04:37:19 - 00:04:59:18 They've suddenly had this 'aha' moment and that then has gone from, you know, an academic or data or IT kind of problem. It's broken out of it and gone into the board to say, well, actually, what does this mean? How will this work? And as people start to imagine what it could do beyond, you know, asking a question about, you know, what recipe do I have? 00:04:59:18 - 00:05:20:13 Or how can I find an answer to a question I could historic could use a search engine for, but save me some heavy lifting organizations to look at it and say, oh, hang on a minute. What manual processes in my organization...What low value repetitive tasks are happening in my organization that this might help me change? So suddenly AI has gone from being an IT conversation to being a business conversation. 00:05:20:13 - 00:05:48:15 It's it's got the opportunity. It's got the ear of the board. And suddenly that's just pivoted the demand and the interest in AI I think in the last couple of years. That is quite insightful. So because I has become the big thing in the world and everybody is talking about AI, there's got to be some, some common myths or misconceptions about AI out there that you've heard give us one or a couple that you've you've heard that you need to clear up and be like, that's not actually the case. 00:05:48:17 - 00:06:11:19 So there's a couple of things that I think, reoccurring in the conversations I have with customers, with, with engineers, with particularly people outside of IT. And one of those is around privacy. And I think that the challenge that we have with AI is the first services that really burst this into the public domain. There's kind of ChatGPT services. 00:06:11:19 - 00:06:31:04 There's first, opportunity where you could just go to a website, sign up for free, try something for free, engage with it and have a human like conversation. But that spread like wildfire, like 100 million users in a crazy amount of time. The interesting thing there is that free service, and I always like the phrase if something's free, you are the product. 00:06:31:06 - 00:06:54:21 That's those kinds of public sites where it's, you know, it's a consumer-grade service. There's no charge. The huge costs sitting underneath those models, like running the infrastructure, running the applications, having train the models. So the reality is in that environment, the value exchange it was happening is the prompts that I give that free service are available to be used to retrain the model to extend it, to make the product better. 00:06:54:23 - 00:07:24:01 So you're giving access to the data that you provide through a prompt to the service provider that is running that service. That's the value exchange. Now that's created this perception in people's minds that AI isn't private or safe or secure. And I think the reality is, when you do this in an enterprise context, you can absolutely run those models in a ring fenced way, the same way you'd run a database platform where it's isolated. 00:07:24:07 - 00:07:41:09 It's not sending data back to the model provider, it's secure and it's yours. And that enables you to do things. Bring your private data combined with the intelligence that the model has been trained on with public data. And that's what builds builds a system. But it doesn't have to be a system where you're losing control of that data. 00:07:41:13 - 00:08:02:22 So I think there's a lot of FUD around that fear, uncertainty and doubt. And it's up to us as technologists to help dispel the myths and separate where that might be happening in certain domains. That free service is public services. Maybe that is happening, but in an enterprise it scenario, you absolutely can put the security and privacy guardrails around it to meet the kind of enterprise controls that you'd expect. 00:08:03:00 - 00:08:36:10 Whilst reaping the benefits of the AI productivity gains, that you could have. So I think that that to me is the big one. Awesome. Thank you. So, because you said that, you you talked about AI, in industries, and how it's used. And I really like the analogy with the database. So for us, with MySQL, we really enjoy, the databases, could you, paint a picture of how AI is being used across the industries, or is it just specific, or can we use it, in different ways? 00:08:36:10 - 00:08:58:07 And, now it's a great question. I think, like most technological innovations, the thing that is most disruptive about AI is it has an opportunity to be a general purpose technology. And so if I think about things like the internet and electricity before it, electricity is a general purpose technology, right? It's one thing that it is it's ubiquitous in society. 00:08:58:09 - 00:09:21:11 But it's used for many things. Right? It's used for the lights in my room, for the microphone, the router that's routing this, this conversation to you. It's also used to heat my house. It's it's used to generate, to run factories. It's a general purpose technology. The beauty of that is it's power and it's ubiquity and it's up is only constrained by the imagination of people who take electricity and think about what problems could I solve with it? 00:09:21:13 - 00:09:46:16 I think I will be very similar to that. But it's up to us in industry, in technology to invent ways to use this, that are productive, that deliver value for our organizations or for society at large. And the real opportunity there is is boundless, is captured only by our imagination. What I am seeing is there at the very specific first mover type, use cases that are happening. 00:09:46:20 - 00:10:08:10 And they might be things like, you know, drug discovery and protein folding, like highly academic, data science led things. They're moving really fast because those are things where data scientists were already doing lots of work, they were already doing machine learning. They were already up and running with AI. What I'm noticing is that enterprise adoption is a different kind of material, right? 00:10:08:10 - 00:10:30:00 It's a different kind of IT problem to go solve. So what we're seeing is enterprises are experimenting. They're doing lots of pilots. They're they're kind of engaging in, you know, the art of the possible. How could we use this in our organization? What things do we not know about how to do this? We haven't trained our organizational muscle to be able to go from idea to pilot to production yet. 00:10:30:02 - 00:10:51:11 So what I'm seeing is organizations look at human in the loop scenarios. So they're starting with applications where AI is helping a task that already happens to happen a bit more efficiently, a bit more effectively, or drive more coverage. And my favorite example of this was, is in regulated industries where actually, you know, organizations are a bit fearful of upsetting the regulator. 00:10:51:11 - 00:11:10:22 And, you know, we're using AI. And what's the governance challenge with this? I work with a few organizations. You've actually turned that on his head. And what they've said is, how can we use AI to improve our compliance, and regulatory frameworks. So they were looking at this and saying, well, you know, today we have a contact center and we have a team that listen to all the recordings. 00:11:10:22 - 00:11:30:19 Well, actually, they listen to 5%. They sample the recordings and they look for compliance challenges. And then they use that to inform how they educate people and report with compliance, status. So they said, well, actually, why don't we have I listen to all of the calls and then the team that were previously only listening to 5% can go and mark the AI's homework. 00:11:30:21 - 00:11:47:08 And this creates value because now I've improved my compliance perspective on screening all of my phone calls. And the people who are listening to those calls and marking the AI's homework, they can improve and iterate on the model and make it better over time. So we have that human in the loop. So it's augmenting the capability of a team to do something and improving the outcomes for the organization. 00:11:47:14 - 00:12:09:11 I think when you start with use cases that are in that kind of domain, the organization can learn, can adapt and then understand how do I apply this to other problems. And it really has to come from what's the biggest problem in my organization? What's my strategic objective? How does that relate to a data strategy, to an AI strategy to go solve those business problems I want to solve? 00:12:09:14 - 00:12:31:19 And that's the real connective tissue here. It's not a science experiment. It's not AI for the sake of it, just like it wasn't data for the sake of it. It's about data to solve a business problem, help us take action in our organizations. That's awesome. So the three of us obviously work for Oracle, and there's been a lot of news about what Oracle wants to do in terms of AI. 00:12:31:19 - 00:12:58:02 And, you know, are we currently a significant player in the AI world or are we going to get there eventually, do you think or, you know, is it is there is there some other path for Oracle in terms of AI? I think Oracle has a unique position in a number of ways. So if we think about the news that you're talking about yeah, there's lots in the press today about the huge investments that we're making, the giant partnerships that we're doing. 00:12:58:04 - 00:13:21:13 These are about the industrial scale infrastructure that will be needed by organizations, both to train the next generation of these models, but equally to run and inference them. So if you're an organization that wants to consume AI, you want to do that scale. You need that bulletproof, high performance, low latency infrastructure that is secure and robust in order to run the workloads that are powered by AI. 00:13:21:15 - 00:13:43:20 If you're going to do this in an enterprise fashion, you're going to want to do that in a robust, secure, resilient fashion. So building out that infrastructure, the Oracle Cloud infrastructure that we have today, the strong partnerships we have with, GPU providers and software vendors like Nvidia, these are the kind of raw foundational capabilities at absolutely epic scale that are critical to this success 00:13:43:21 - 00:14:21:20 in AI and Oracle's right at the front of that. Interestingly, though, it's not just about tin in data centers. It's about the software stack. It's about the ability to take that raw compute and augment it securely with robust data practices, bring data into the world, bring AI to where that data lives today. That's where I see Oracle being really powerful between huge database platforms from Oracle to relational database platform to MySQL, these are key capabilities and your key software assets that will help organizations unlock the power of that infrastructure and bring it to life in their organization. 00:14:22:00 - 00:14:53:00 And then at the other end of the spectrum, you have, SAS applications at fusion. These are the business process tools, the systems of record, the organizations trust to do work for their organization. They have key elements of data, and they operate they run business processes in your organization. So the ability to surface the outputs of the AI and applications that business users use so they can understand it, use the, you know, interact with the data, glean insights from it, leverage the power of AI to take action for and with them. 00:14:53:02 - 00:15:13:21 That that combination right across the stack, I think is where Oracle is uniquely positioned. And and hence,I am here. Excellent. Yeah. Very nice to see that Oracle actually is a big player in the AI and had the opportunity to see plenty of, of stuff on that tool like the data centers, who we created the, for it. 00:15:14:03 - 00:15:44:00 And, so and yeah, in MySQL, we, we already also see with MySQL HeatWave what brings to to AI there. But, so with that position of of Oracle, going on lot on AI, do you think it will impact, the, the product portfolio, of Oracle, like some stuff to, like, MySQL we know about it, but for other products, do you think that will also impact them? 00:15:44:02 - 00:16:08:19 This, this role of Oracle in the industry? I think it will. I think it will it will bring a new gravity to, to the solutions that we offer. I think the other component, and you're seeing it with MySQL, you see it with Oracle, you know, actually, how do we take the greatness of the database platforms that we have and extend that to simplify organizations use of new technologies? 00:16:08:23 - 00:16:31:13 And you know, my favorite example of this is how do you enable the existing database to do more of the tasks you need in an AI world? So with that, I'm thinking about vectorization, storage of vectors, the ability to run inferencing close to the data. I don't have to pull all my data out of the database just to then run some inferencing over it. 00:16:31:18 - 00:16:58:15 How do I bring that AI capability directly to where the data lives? So I think we're seeing that with lots of the product innovations. And we're also thinking about like what does this mean to governess. You know, if you have a solution where, you know, you've become used to as an organization governing and managing a relational database, how do I then work in a world where I have unstructured data, structured data I have now vectors, it's these are all living in different store data stores. 00:16:58:17 - 00:17:13:12 How do I govern and control that? How do I make sure that I'm keeping that data in in sync? How do I make sure that I've got my GDPR compliance correct? A customer wants to be forgotten. I've now got more places that I need to forget. The customer. I, you know, update that data because it has to be correct. 00:17:13:14 - 00:17:42:02 So I think this concept and we see it across the MySQL platform, we see it across Oracle database. Actually by bringing the vectorization, the vector storage, the vector generation, the the ability to query right into the database engine, you simplify the operational management, you simplify the governance of that model. It makes it easier to secure, to manage access in ways that your organization is already familiar with, by managing a MySQL estate or by managing an Oracle platform. 00:17:42:06 - 00:18:04:09 So so suddenly you're able to expand the scope of the things that you do without it bringing extra operational and governance, complexity into your organization. So it's already influencing our product portfolio. It's already changing the way...
/episode/index/show/d0cd255f-ccaf-4b55-a7da-5825f8230161/id/37551690
info_outline
A Rockstar Speaks
03/17/2025
A Rockstar Speaks
MySQL Rockstar, René Cannaò, drops in on Fred & Scott to wax philosophical about the success of MySQL, the MySQL Community, and his inspiration for ProxySQL ----------------------------------------------------------------- Episode Transcript: 00:00:00:00 - 00:00:36:10 Unknown Welcome to Inside MySQL: Sakila Speaks, a podcast dedicated to all things MySQL. We bring you the latest news from the MySQL team, MySQL project updates and insightful interviews with members of the MySQL community. Sit back and enjoy as your hosts bring you the latest updates on your favorite open-source database. Let's get started! Hello and welcome to Sakila Speaks, the podcast dedicated to MySQL. 00:00:36:14 - 00:01:01:13 Unknown I am leFred and that is Scott Stroz. Today we are happy to welcome René Cannaò to our podcast. René is a well-known figure in the MySQL ecosystem. He's mainly known as the author of ProxySQL, which he founded in 2016 after developing it since 2013. René is one of our rockstasr and recently received his award during the last Pre-FOSDEM MySQL Belgium Days. 00:01:01:15 - 00:01:25:11 Unknown Welcome, René. Hi, Fred. Thanks for the introduction. I'm very excited to be part of this podcast. And, yeah, it's I'm way I also very much appreciate the MySQL award that I received the early last last month. It was a nice surprise, and I'm very excited to be part of this growing community. Awesome. Thank you René, it was great meeting you last month. 00:01:25:13 - 00:01:48:07 Unknown So, as a longtime member of the MySQL community, do you have any thoughts on how MySQL became the most popular open source database that powers the internet? I don't think that MySQL popularity can be attributed to just one single factor, but I think the combination of factors that made, MySQL so popular as an open source database that is powering the web. 00:01:48:08 - 00:02:17:19 Unknown So, I would say that the probably the very first factor is its simplicity and easy to use, that it made it accessible to all developers of all levels, especially during the early days of the web. So, everybody could have access to MySQL and install it. And this made possible for MySQL to be part of, that very classic Lamp stack in which we had the Linux, Apache, MySQL, and then PHP, Python or Perl. 00:02:18:01 - 00:02:47:14 Unknown So, MySQL was part of this stack, and this allowed it to have, widespread adoption, especially for web application. And, you know, this, this sort of created, positive feedback loop because, as more, users were using MySQL, then the product was becoming a bigger product and then more users were using MySQL. So, you know, this created an absolutely, feedback loop. 00:02:47:19 - 00:03:21:04 Unknown And I think another factor that absolutely affected, the popularity of MySQL was the fact that, not only was easy to download it easy to install, but it was also very reliable, very, very good performance for web application. And it was focused on what the traditional and nontraditional, transactional and non-transactional, workload. So, everybody could make it, and could use it no matter how big were their specific web application. 00:03:21:05 - 00:03:51:11 Unknown And, finally, I think, another important factor was the fact that it had a very, fast growing community around it. So, this absolutely is one of the factors that made it, one of the most popular open-source database. Awesome. Thank you. René. So, as we can hear, you know, very well, MySQL, you're around for a long time in the community, but, it seems that you also worked at MySQL, isn't it? 00:03:51:11 - 00:04:19:05 Unknown Yes. That's correct. As I said, so if you correct, have been in the MySQL ecosystem for very long time, I think I started using MySQL in production in 2004. I was one of the very, few people that saw getting the MySQL certification. Actually, I think it was I was, number 23 with the MySQL Cluster certification. 00:04:19:09 - 00:05:04:01 Unknown So, I've been using my secret for very long time. And as you correctly mentioned, I also worked for MySQL from 2008 till 2011. And, I was part of the MySQL support team. Immediately after the acquisition from Sun. And there was that the last 11. So, after, the acquisition, for Oracle. And I would say that as me, I have been very fortunate in, working, team member of the MySQL support team because there I had the opportunity not only to work together with excellent, and very knowledgeable people that were working in my same team, in the MySQL support team. 00:05:04:06 - 00:05:27:19 Unknown But, I also had, let's say easy access to developers or MySQL developers. So, if there was anything that none of us in the MySQL support team were able to answer about some specific internal of MySQL, it was it was extremely good that we always had the some developers who we could ask for feedback or for clarification. 00:05:27:21 - 00:06:07:09 Unknown And I would say that, I was also very fortunate in working in, in the MySQL support team because during the time I get, exposure to how customers are using MySQL in, in a variety of environments. So, from very basic environment to extremely complex one. So, I had I gained experience in helping them on how to tune MySQL the right way and how to address device, ability challenges and how to make sure that their MySQL environment and their full stack was, having higher ability. 00:06:07:15 - 00:06:47:06 Unknown So yes, I would say that, it was an exciting time in my career. That's fantastic. , we mentioned that you created ProxySQL. Can you give us a high-altitude overview of what ProxySQL is and what what gap was it meant to fill when you started creating it? Yes, sure. So, as I mentioned before, I was working for MySQL from 2008 to 2011, but also before I joined MySQL support, I was consulting and doing work related to MySQL and same thing after. 00:06:47:08 - 00:07:12:21 Unknown After I left MySQL, I was still doing consulting for users of MySQL large infrastructure. And during all those years, during my career, until I start ProxySQL, I noticed that there was, consistent pattern of, common challenges that the users were facing. And sometimes they don't even they didn't realize it that they were facing those challenges and those challenges. 00:07:12:21 - 00:07:37:07 Unknown were related to connection management, query routing, query caching and overall scalability. So how to be able to make sure that that database infrastructure is able to scale. And, you know, sometimes it was possible to tune MySQL in the right way to get the maximum performance out of it. But as a whole it was still difficult to be able to route traffic on. 00:07:37:08 - 00:08:05:12 Unknown Or if route traffic on the flight or managed connection properly. So, this is when I started writing ProxySQL. So, basically it was a side project that was born out of necessity. I needed a tool that was able to performs the action that I wanted to perform. That was a, as I was saying, making connection, performing override caching and so on. 00:08:05:14 - 00:08:23:14 Unknown So, this is how it started. So, it started, a very simple prototype. Initially, I started looking around. I didn't want to start a new project at the beginning. So, at the beginning, what I did was looking around, trying to find the right tools, for what they needed. But there was nothing really available. 00:08:23:16 - 00:08:47:11 Unknown That was MySQL Proxy back then, but it was, sort of an abandoned project. I tried to play with it, but I didn't manage to get, anything from it. So, this is where I said, okay, it's time to start a new project. So, I start this new project, I push it on GitHub, and, initially, I was the only one using it, to my customers. 00:08:47:12 - 00:09:21:13 Unknown So, you know, we it went from development to production straight away because the users I was, managing, they immediately got ProxySQL in their environment. So, I knew that was solving their specific, problem. And, you know, people start using it to so they start getting traction and that's, contraction and then adoption, automatically grew. And from a side project, it quickly evolved into a full-fledged product and eventually into a company. 00:09:21:15 - 00:09:53:21 Unknown Awesome. Thank you, René. There is, urban legend, about about it that, you, share with, some people, before developing it or just at the start, at FODSDEM on the beer coaster, you shared the architecture of a ProxySQL with some friends. Is it true? Yes. There are a lot of a lot of stories on, you know, this goes back to the the initial question about the MySQL community. 00:09:53:21 - 00:10:31:12 Unknown I think the MySQL community is a very vibrant, community. So, it is not uncommon, that, while drinking or a beer, we share great ideas or we create some new design or, we brainstorm about a new product. And this is what I love about FOSDEM and Pre-FOSDEM the ability to meet with, like-minded people that, they are very engaged in the, the MySQL ecosystem, and they are always looking forward to improving the product and all the products around MySQL. 00:10:31:14 - 00:10:57:23 Unknown Excellent. So why we are discussing, about FOSDEM, you could attend, so on the last, MySQL, dev room and at FOSDEM, you could attend the very first session about the MySQL routine guidelines. So, what are your thoughts about, this, completely new feature in MySQl Router? Well, I think it was a very interesting presentation. 00:10:58:01 - 00:11:45:02 Unknown I think it was, very exciting. And, for the people that are listening this podcast and we are not familiar with, what the MySQL Routing Guidelines say. So, I will give a very brief introduction. I think that, routing guidances is a great, great step forward for managing query distribution in MySQL architecture. You know, I, I spoke before about ProxySQL, how one of its main features is about, routing traffic and, because routing traffic has always been, has always had a critical role in high availablity setup and scale out environment when there are multiple MySQL server either co-located or geographically spread. 00:11:45:04 - 00:12:23:03 Unknown And so the MySQL routing guidelines, what allow is to define routing in a way, complex, you know, way more complex way than how previously was possible in MySQL out there. So MySQL router the routing was extremely simple. And now with MySQL routing guidance, this is becomes more complex and more dynamic and more declarative. So, this, routing guidelines allow administrator to define destination and route using expression. 00:12:23:05 - 00:12:49:17 Unknown So, it allows more granular control over how client sessions are directed to backend servers. So this is what guidance is and routing guidance is. And I was very excited to see this presentation. One of the reasons why I was so excited is that basically, this approach aligned a lot to with what we have been doing in with, with ProxySQL for years. 00:12:49:21 - 00:13:14:22 Unknown So, the ability of having complex, routes that allow the administrator of a MySQL router or ProxySQL to define the what to do with, with the traffic and where to send the traffic and what operations need to be performed. So, I'm very excited to see that, MySQL is officially embracing, more advanced routing model. 00:13:14:22 - 00:13:45:16 Unknown I think that this will allow to standardize how, routing is being defined. So, I'm very, curious to know how users will start utilizing this routing guidelines and also how vendors will adapt to, to this new solution, proposed by MySQL. So, I'm pretty sure it will affect also us, ProxySQL. So I'm very excited to see how this is going to evolve. 00:13:45:18 - 00:14:11:23 Unknown And finally have, one further comment on this. That is one of the issues that we have been seeing with ProxySQL over the years as well, the ability of creating rules that are very flexible for some time and make it very difficult to combine the flexiblibility from one side and the simplicity from the other, because, you know, the more flexibility you have, the more the config, the more complex the configuration can become. 00:14:11:23 - 00:14:35:20 Unknown So, it's very interesting to find the right balance between simplicity and, flexibility. Now, René, thank you for joining us. I appreciate it. As I said, it was it was great meeting you at FOSDEM. It was great meeting so many of the the community members whose names I had recognized for for quite some time and, actually finally get to to to meet a lot of you in person was was really pretty cool. 00:14:35:22 - 00:15:04:07 Unknown That's a wrap on this episode of Inside MySQL: Sakila Speaks. Thanks for hanging out with us. If you enjoyed listening, please click subscribe to get all the latest episodes. We would also love your reviews and ratings on your podcast app. Be sure to join us for the next episode of Inside MySQL: Sakila Speaks.
/episode/index/show/d0cd255f-ccaf-4b55-a7da-5825f8230161/id/35735115
info_outline
The Bug Whisperer
02/13/2025
The Bug Whisperer
For this episode, Fred and Scott are joined by Laurynas Biveinis - one of the most prolific individual contributors to MySQL Community. Take a listen as Laurynas discusses the process he uses when he discovers bugs and how he sets up tests for the engineering team. ----------------------------------------------------------- Episode Transcript: 00;00;09;14 - 00;00;36;00 Unknown Welcome to Inside MySQL: Sakila Speaks, a podcast dedicated to all things MySQL. We bring you the latest news from the MySQL team, MySQL project updates and insightful interviews with members of the MySQL community. Sit back and enjoy as your hosts bring you the latest updates on your favorite open sourcedatabase. Let's get started! Hello and welcome to Sakila Speaks, the podcast dedicated to MySQL. 00;00;36;07 - 00;01;13;06 Unknown I am leFred and I'm Scott Stroz. Today we are thrilled to welcome Laurynas Biveinis to our podcast. Laurynas. He's a highly respected software engineer and a seasoned expert in database technologies, particularly MySQL. With a rich background in database internals, performance optimization and open source development. Laurynas has contributed extensively to the MySQL ecosystem. He has played a key role in announcing most performance and reliability to his work on project like the Percona server and other database innovation. 00;01;13;08 - 00;01;45;08 Unknown We are excited to dive into this highlight on MySQL, his evolution and the future of the database technology. Laurynas, you have been extremely active in helping improve MySQL and since April 2011, you have reported 444 bugs. First of all, I love the symmetry of the number of 444, but can you like, give us, a brief walkthrough of how you go about reporting the bugs? 00;01;45;08 - 00;02;00;25 Unknown Like, like what type of testing do you do? Do you set up some type of test framework or, or something? Because obviously, you know, you need to make sure that it can be repetitive and you have to report that stuff to, to the team. But just walk us through like your mental process that you, you, you do for that. 00;02;00;28 - 00;02;30;28 Unknown Hello. And, thanks for having me here. So to, to to answer the question about bug reporting. Whenever I notice that something is off, and I make a note of it, and I return to it later, and the majority of my bugs come from, either, documentation reading, either from the source code reading or from, running the source code, in the in a test framework. 00;02;31;00 - 00;02;52;18 Unknown So, the test framework gives something that, creates reproducible test cases. And if I can write one in the test case, in the, in the test framework, I do that and I submit that with a bug reports. And I know that your team immediately can, they can tell me whether they produce it or is, that they need something else for me. 00;02;52;21 - 00;03;20;04 Unknown So. So you are using MTR, as the the same framework as we do? Yeah. Most of the time I'm using MTR. So, but, so about all that, huge number of bugs that you report, you are also one of the most prolific contributors of my SQL with, 84 contributions in MySQL 8. So, why are you contributing so much and what type of contribution do you do usually for people that doesn't know you? 00;03;20;06 - 00;03;48;09 Unknown Well, so, these are usually bug fixes. Most of the time small but sometimes larger too. And over the years there have been a few performance features contributor to. So the thing I like about contributing is that,contribution makes that code less of my problem and more of your problem. So, it's like a gifting a puppy. 00;03;48;11 - 00;04;17;27 Unknown And so now you have to take care of it, although you are happy you received it. I love that analogy. That's a that's a that's a analogy about open source, contributions. That's great. So I've seen that you, recently have been blogging quite a bit about, MySQL and Mac OS, which interests me because for work I use, a mac and obviously I have to run MySQL on that platform. 00;04;18;00 - 00;04;48;15 Unknown But usually MySQL is run on Linux. That's a probably. Linux is probably the most popular operating system on which to run MySQL. Why do you think that is? Well, it's won the server wars. Hasn't it? And with the, the newer with the new features, with, with the BPF and you're in it's, it gets better every day and there is no real competition for it in the server space. 00;04;48;18 - 00;05;15;22 Unknown But the thing I love about Mac is that, development is easier for me on the Mac, and the hardware is very good. The build times are excellent on, on the on the Apple silicon machines. So I like that, I can do it with the least friction and with the, the best the turnaround time from typing to testing. 00;05;15;24 - 00;05;33;19 Unknown So that's why I'm trying to do development on Mac to the extent that I can. Obviously, I have Linux machine store and obviously test there as it needs coming, but as long as I can stay on Mac, I'm happy. What I like about using a mac is that it is closer to a Linux environment than Windows is. That's true. 00;05;33;24 - 00;05;53;13 Unknown Like, you know, I, I could run a lot of the same commands on my Mac that I would run on a Linux instance, and they would both work exactly the same. You can't say that for windows for the most part. I haven't tried windows with the double WSL. Maybe it gets that true, but, I'm happy where I am and see, no need to switch. 00;05;53;15 - 00;06;18;13 Unknown So, Laurynas, so you are very active in the MySQL ecosystem, as we can see, and, for several years now, but,it seems you have been, away from the dolphin community, from August, 2019 to January 2020. So, because,I check the contribution, I check the bugs. And then you are back. So we are very happy of that. 00;06;18;17 - 00;06;53;25 Unknown So how do you explain this? Did you take some break or what happened? Well, it's like, explaining a gap on the CV in the job interview, isn't it? Yes. So, so I had that two and half gap years where I was not working on MySQL, but I was working on the, the distributed, NoSQL key/value store, Aerospike and, did some do some engineering there, but, I think I missed MySQL and and I came back then you saw the light again and you follow it. 00;06;54;00 - 00;07;17;27 Unknown So one of the biggest changes in my SQL last year was the release of, the LTS that made a lot of enterprise users happy. What do you think about it? And I'm very lucky that as a software engineer, I don't have to run my SQL only to, to write code, but, I the I have talked to users, and I and I, I feel happy for them. 00;07;17;28 - 00;07;46;00 Unknown I think the rolling release model or fato times had its challenges and it was challenging to do patch level upgrades, which were not really patch level upgrades. So the, LTS model I would say is a welcome change. And and I'm, I'm happy that you did it. Thank you very much, Laurynas. And, to end, this podcast, I would just congratulate you because you just have received, a Rock star award. 00;07;46;07 - 00;08;07;27 Unknown So, congratulation. Thank you. That's that's, that's an honor. We are very happy to have you in the community. And everybody, likes you in the MySQL team, but also, around MySQL, when you talk to people, outside, MySQL. But they are part of the community. They all have, very kind words for Laurynas. 00;08;08;00 - 00;08;25;20 Unknown So, again, congratulations. And thank you very much to have you today with us, the podcast. That's a wrap on this episode of Inside My SQL: Sakila Speaks. Thanks for hanging out with us. If you enjoyed listening, please click subscribe to get all the latest episodes. We would also love your reviews and ratings on your podcast app. 00;08;25;23 - 00;08;35;07 Unknown Be sure to join us for the next episode of inside MySQL: Saklia Speaks
/episode/index/show/d0cd255f-ccaf-4b55-a7da-5825f8230161/id/34985295
info_outline
What's in a name?
01/30/2025
What's in a name?
Pedro Andrade joins Fred and Scott to talk about how MySQL's mascot was named. Pedro shares a conversation he had with Ambrose Twebaze where they discuss the competition where Sakila was given her name. ------------------------------------------------------------- Episode Transcript: 00;00;09;13 - 00;00;32;08 Welcome to Inside MySQL: Sakila Speaks a podcast dedicated to all things MySQL. We bring you the latest news from the MySQL team, MySQL project updates and insightful interviews with members of the MySQL community. Sit back and enjoy as your hosts bring you the latest updates on your favorite open-source database. Let's get started! Hello! 00;00;32;09 - 00;00;55;07 Welcome to inside MySQL: Sakila Speaks, the podcast dedicated to MySQL. I am a leFred and I'm Scott Stroz. Today we are diving into something fun. Mysql’s beloved mascot Sakila the dolphin. Sakila represents more than just the logo. It's a symbol of a global community. It's open-source spirit and its dedication to efficiency and speed in the database world. 00;00;55;11 - 00;01;15;24 But what's the story behind Sakila? How did a dolphin become the face of one of the most widely used database management systems in the world? And what significance does Sakila hold for the MySQL community, and how does it inspire innovation? To learn about the name of this iconic dolphin, we have Pedro Andrade a long-time MySQl-er of 17 years. 00;01;15;25 - 00;01;39;21 So, Pedro, can you tell us how Sakila became MySQL’s mascot? Was there any particular reason behind choosing a dolphin? Yeah. Hello everyone, this is Pedro Andrade. So, the reason that the dolphin was chosen as a mascot is it represents, the database. Ease of use. So, friendliness. Right? Speed and agility. Because, as we all know, dolphins are very smart creatures. 00;01;39;28 - 00;01;59;29 So, the name Sequela as an interesting background, it was choose from a naming competition. And I think you personally know the winner. Can you share more about the story, Pedro? Sure thing. So, as you mentioned, I've been with MySQL for a long time, and I’d always been very curious about the experience of the of the person that chose the name. 00;02;00;04 - 00;02;26;17 In the early days of MySQL and through community sense, what MySQL did is they opened a worldwide contest that was called, “Named the Dolphin Contest”. And so, we had submissions from all over the world. And the way the contest went is, the winner would win a couple of T-shirts and a Palm Pilot 3C, which, for those of you that remember, that was the color Palm Pilot, which was a very advanced technology at the time. 00;02;26;23 - 00;02;47;26 So, I did track down the winner. His name is Ambrose Twebaze. It took me a long time because he's not really on social media. So, after a couple of years of digging and searching, I found him, and he is in, Eswatini. Would you say a landlocked, kingdom in Africa? I spoke to Ambrose recently. 00;02;47;28 - 00;02;56;04 And I have some, some, interesting questions for the rest of the community to learn. 00;02;56;06 - 00;03;34;21 Thank you. Thanks again for talking to us. As I mentioned, MySQL is turning 30, in 2025, so that's coming around the corner. And we wanted to just, just revisit, the particularly the, the mascot, our mascot, the dolphin, which was name is Sakila, as you know. And you, you named it. So, this goes back to it and correct me if I'm wrong, but from from what I read, the contest itself was announced in 2001, and then, the submission or the, you know, the, the final, submission was, was chosen on, on 2002. 00;03;34;21 - 00;03;54;21 Is that right? So it was in 2002. That is that sound about right when you submitted the name? Yeah. Yeah, I think it took some time, but eventually it came through email. I saw where it I was very surprised because, I mean, when you enter something, there are so many people that enter these competitions. You are not expecting anything out of it. 00;03;54;21 - 00;04;14;22 I mean, we always enter competitions, so for the best or just you do it for the sake of it. Okay, let me just do this. And, what ends up ends. And so ,I did receive after a long time, I received an email that say, no, your name was chosen as the winning. Then they asked a few questions. 00;04;14;22 - 00;04;53;26 If I could write a few things about, the name, what it means. The name. This, basically, it's from Swaziland. Now, this was it is now rebranded itself as, Eswatini. Sakila, basically, it's a traditional, I don't know, like, stick for warriors was warriors, that used so actually it's pronounced “sagila”. So I thought when I was writing there, because, the people who receive this name are not from Africa. 00;04;53;26 - 00;05;18;04 They don't know how to pronounce this name. So it's being pronounced as "Sakila”. Okay. But for us, here in southern Africa, here. So I'm still in Eswatini, by the way. It's pronounced as, “sagila”, but it's very good because the name that came up, maybe that was the best, because now that means it's unique. It's not. 00;05;18;09 - 00;05;38;03 It's no longer what I thought it was going to be, but, in terms of pronunciation, but it's still the same name because we pronounce it k. Here is a G “sagila”, which is sort of like a stick. But it's fine. I think that was the best. Sakila also sounds very nice and fuzzy. It's unique and actually. 00;05;38;03 - 00;05;54;23 So that is, my favorite part about about the whole story. So, so first, I don't know if I probably told you, but when I, when I finally did find you, it really had been a couple of years that I, that I been searching and it and I'm trying to remember where exactly. Fine. Because you are not on LinkedIn. 00;05;54;25 - 00;06;13;06 And I was searching the web, and if I'm not mistaken, I actually found you, a song that you had posted or a track on Mixcloud. I think that's what it was. And I probably reached out to you through there or something like that. And then when we finally talked and, you told me that the name was actually meant to be "Sagila”. 00;06;13;06 - 00;06;33;02 I think you said it was a typo. It was. It was just, that much more special. And. Yeah. So you and I have looked up, “sakila”, as you mentioned, it's a walking stick. And so let me ask you, when you, that. Well, how did you hear about the contest? First of all, did you just see the the posting on MySQL.com or how did you learn about the name The Dolphin contest? 00;06;33;04 - 00;07;00;02 I think I frequently used to go to MySQL.com, sometimes download the latest MySQL. And so I read about it then. Then I decided to to join the I mean, Eswatini, do is to be called Sagila. Like, you know, and some sort of a tool. It's a tool based, I believe also, MySQL is sort of a tool in some sort of application. 00;07;00;02 - 00;07;27;11 It does. It has some purpose in the applications. So I thought, well, this is a tool. Let's, maybe it's a suitable name for tool like that. Yeah. It's good. And let's see. So you and so you had, you had been using MySQL. What about more generally speaking on open source. Do you, have you ever contributed code or, you know, you contributed to MySQL or, or any other open-source software? 00;07;27;13 - 00;07;51;22 Are you mostly a user or do you develop or do you, have you submitted any changes of code to, to open-source software? Open-source software – I am more like a user, just like, then I was using my database because we are using it for as a PHP backend because MySQL and PHP. I don't know what you'd call that. 00;07;51;27 - 00;08;25;07 In the States, I don't know, it's maybe like, if you're talking about food, I think it's what you guys call is it's is it “mac and cheese”? So they go together sort of the LAMP stack? Yes. In the technical terms, yes. So it was a tool of choice in terms of if you the PHP, you had no choice but to sort of have your back end is MySQL the other option, which cumbersome to work with. 00;08;25;09 - 00;08;48;20 And in terms of me writing code, no, I'm not that fancy. I'm not that sophisticated that I can write. Well, changing code. No, I'm just, the only way is to interact with, if in MySQL, it's still the same way if I have, like, we have, websites that we sort of develop in WordPress. 00;08;48;20 - 00;09;08;17 So the back end, there are always going to be, again, MySQL. What version of MySQL are you running these days, like a 5.7 or an 8 dot something? Now it's very tricky. I'm not sure because we do not host this and we sort of like it's in the cloud. It's whatever on they have, but the others have the latest. 00;09;08;19 - 00;09;39;21 I would have to look in the details, but, you know, this ISP is running the latest because for some reason, for security purposes, the upgrade to PHP, I see, I think 8.2 or something, but MySQL I really haven't really seen the actual version. But it's also it should also be the latest because the others like does something behind not necessarily what's out because the others prefer to use as a production release or something. 00;09;39;24 - 00;10;03;21 Yeah, I'm not really particular about that, but, the latest, that's what I can say. It might be the one version behind, but, the latest. Well, I mean, so so you have been you have been using MySQL probably. I mean, so before 2001. Right. So, 20 plus years. So for a long time. Yeah. Yeah. In all the because, I do I'm sort of like a web developer. 00;10;03;21 - 00;10;27;19 But in terms of web, it's always this one has been there as long as of in fact, it's tied in with WordPress cos WordPress is sort of like the more and has become popular, the more MySQL also the open-source version also became popular. So that's closely tied together. So they've all come along with so like right now WordPress is sort of the number one content management system I think. 00;10;27;21 - 00;10;48;20 And and so so MySQL is still, you probably know, the the most popular open source database. And what I mean by that is it's just it's really the most widely deployed, open source database out there. And this is, you know, set by independent studies. So I it is still, you know, everywhere and going strong. 00;10;48;20 - 00;11;09;24 And so let me ask you this, when you won the contest, so you got the notification over email. And we also talked about this last time because I remember the, the prizes, were, I think a couple of t-shirts and a Palm Pilot 3C, which was very fancy at the time. It was a color version of the, of the Palm Pilot. 00;11;09;24 - 00;11;28;08 And I guess maybe for some of the people that might be hearing this might not know what that is, but it was a digital organizer I guess. Right. So you would call it, can you talk a little bit about the, the I thought that was very interesting to the experience of, eventually getting the prizes, over to you because I think it took a long time, right. 00;11;28;08 - 00;11;50;07 with customs? That took a long time, they mixed up the addresses, and when I, I don't know when the Palm Pilot it came out, it was the latest at that point, three years later, when I got it, I was like, oh, okay. So this is it. And I'm like, what the. And I'm like, what am I going to do with this? 00;11;50;09 - 00;12;17;04 So I mean, look at smartphones. But when you look at the Palm Pilot, that's actually I think that's what sort of contributed its own in terms of bringing smartphones into the mainstream. So it was the good device at the time. It's just that, it was not a phone that's sort of like an organizer, digital organizer of some sort. 00;12;17;06 - 00;12;53;29 Yeah, I had one myself, the, the black and white one. I never got the color one, but I, I remember the stylus. The stylus was kind of exciting, right, because it was a new thing, right. To to just to the touch screen with a little pen or whatever. Yeah. And then, what about, you know, coworkers or family or friends, do they know, or what was their reaction, at the time or now, if any, to you winning the the contest and naming the mascot for the most popular database software in the world? 00;12;54;01 - 00;13;17;22 Okay, many guys knew in terms of when they would Google me, I don't know, for some reason they would find it, in some way, the sort of like in Africa, open source is big in the world, but it might be much bigger in Africa in terms of, it's if you look at the LAMP stack. Oh, well, it's big, big time here in Africa. 00;13;17;24 - 00;13;40;12 Yeah. It's deployed widely, especially for small medium enterprises. Many people are using, they're using that stuff. So like in terms of so people they know because when they go through the documentation at that point, when the documentation was out, it was at the beginning, the first thing is that MySQL the winning name, it was up there. 00;13;40;15 - 00;14;04;04 It was not needed. It was just up the the first few pages when you read it was right. The so when somebody asked me, they tell me, oh, you did this, this somewhere really like excited for me. Yeah. And happy for me. The only thing is that, like I said, the prizes came much, much later, but the excitement has already died down. 00;14;04;04 - 00;14;22;02 And I thought, oh, well, maybe they got lost, but they just had the wrong address trying to deliver to the wrong place. Yeah, well, what about. What about the t shirts? Did you get those? Yeah. There were. Those would be nice. You know, I think MySQL designs good t- shirts. At that point, I don't know these days how they are doing. 00;14;22;05 - 00;14;40;17 But they were really fancy with the dolphin. Yes. Well, so I'm going to make sure to get you, a couple of updated add ons. Do you still have those from back then? Probably not. 20 years ago. The the original t shirts. I had to give them out. Some people, some people liked them more than me, you know, because I know the dolphin. 00;14;40;17 - 00;15;01;21 But some guys were really they love them, so I give some of them away. Okay. All right. Ambrose. Well, I don't know. Do you have any anything you'd like to tell the the community or the the MySQL-ers, as we call ourselves, users or people that work, you know, continuing to, I guess, created maintain the software. 00;15;01;21 - 00;15;30;06 MySQL. MySQL is such a great product. And I believe that in terms of like us here in Africa, it has been a wonderful product. And, we continue using it. And a lot of businesses have been built around that lamp stack, especially when you talk about WordPress. MySQL and WordPress here in Africa, WordPress deployments. Oh man, I think it's very, very big. 00;15;30;09 - 00;15;58;26 It's better. So MySQL is always in the background. And so it's quite a good product for us. It's Africa, we use a lot of open-source products. So we really appreciate the work that developers are doing at Oracle. So that this product is always updated, has new features, and it's keeping in tune with WordPress, because when WordPress moves up also MySQL I'm sure. 00;15;58;27 - 00;16;37;20 So this is something so you know, in terms of open-source it's been really helpful. And I believe a lot of guys and businesses have been built around MySQL. And those guys are eating right now because of MySQL. Yep. Yeah, I like to I like to always just say that, open-source is is built, you know, by the people, for the people, you know, in some cases like MySQL, you have, you know, a big technology, you know, organization that is behind it, you know, the, the development, updating, support, distribution and stuff like that. 00;16;37;20 - 00;17;04;10 But, but we continue to this day to, incorporate, you know, a lot of contributions from, from the community and as you know, as well, part of the strength of open-source is that since it is, you know, freely available, it gets exposed to every environment, hardware, middleware, software. And so that also in itself is essentially a, a massive, you know, like a testing, if you will. 00;17;04;10 - 00;17;31;04 Right. Just by sheer numbers of deployments. So, it's going strong. And, you know, just is very happy to connect with you again. Ambrose, and greetings from New York. And, we'll connect soon. Again. Thank you. Bye bye. From Bubba in Eswatini. Thats awesome. Thanks, Pedro. So, one more question. If Sakila could speak, what do you think its message to the MySQL community would be today? 00;17;31;06 - 00;18;00;18 I think Sakila. I would tell everybody that, MySQL is as strong as agile and as easy to use as ever, you know, as it kind of as the saying goes, there are many fish in the sea, but there's only one Sakila. Thank you. I have a question for you. Are devinette we see in French? To see if you know, first of all, because some people ask for some time and let's see if one of the, of you guys know is Sakila male or female. 00;18;00;20 - 00;18;25;25 So I have a there's a twist to the to that story. At the heart of the story, there's a twist, right? So while, official documentation out there talks about Saki being a female name, you know, from, Ambrose's home country, it is actually, a typo in the submission. So when I spoke to Ambrose, I asked him if the significance of the name was somebody in his family or somebody close to him, and he kind of, chuckled. 00;18;25;25 - 00;18;47;15 And then he said that he actually sent that as a typo. So he meant to send "Sagila”, instead of "Sakila” with a K and sagila is actually, a traditional African fighting stick or a walking stick, that's made in South Africa. So the reason he chose this is he was he was thinking of something useful, and secure. 00;18;47;15 - 00;19;06;13 Right. So kind of like the database. Right. Very useful. And also, you know, can be used for protection in the case of the walking sticks, in the case of Sakila. You know, it's a secure database. It's a very nice story. Thank you. And it's funny that from a typo, it became, this, most famous mascot, for the database. 00;19;06;18 - 00;19;33;27 It's excellent. So before the dolphin was chosen for represent the mascot of MySQL, the symbol of the database. What, other, feature was, favored to by Monty. Do you know that or not? I personally do not. I don't either. So, Monty wanted to, to be a dragon first, but has the dragon has a multiple, different signification in different culture. 00;19;34;04 - 00;19;56;21 It was not chosen. And the dolphin was chosen after for all the good reasons. We. We heard that before. All right. Thanks, Pedro. Thanks for listening, everybody. That's a wrap on this episode of Inside MySQL: Sakila Speaks Thanks for hanging out with us. If you enjoyed listening, please click subscribe to get all the latest episodes. We would also love your reviews and ratings on your podcast app. 00;19;56;23 - 00;20;01;03 Be sure to join us for the next episode of inside MySQL: Sakila Speaks!
/episode/index/show/d0cd255f-ccaf-4b55-a7da-5825f8230161/id/34959035
info_outline
MySQL User Group Spotlight: MyNA
01/16/2025
MySQL User Group Spotlight: MyNA
Fred & Scott have a chance speak with special guests from MyNA—the Japanese MySQL user association—which is one of the most active MySQL user groups in the world. ---------------------------------------------------------- Episode Transcript: 00;00;09;13 - 00;00;35;05 Welcome to Inside MySQL: Sakila Speaks, a podcast dedicated to all things MySQL. We bring you the latest news from the MySQL team, MySQL project updates and insightful interviews with members of the MySQL community. Sit back and enjoy as your hosts. Bring you the latest updates on your favorite open-source database. Let's get started! Hello and welcome to Inside MySQL Sakila Speaks. 00;00;35;12 - 00;01;04;29 The podcast dedicated to MySQL. I am Lefred and I'm Scott Stroz. Today we are thrilled to have a special guest from MyNA the Japanese MySQL User Association known for their incredible dedication to fostering a thriving MySQL community in Japan. MyNA has been a pillar bringing developers, database administrators, and enthusiasts together to share knowledge, discuss best practices and explore the ever-evolving world of MySQL. 00;01;05;02 - 00;01;31;11 In this episode, we'll dive into the origins of MyNA, their role in supporting the open-source database ecosystem, and their vision of the future of database technology. Whether you're a seasoned MySQL Pro or just curious about its vibrant global community, this is the episode for you. Today we have Kei Sakai with us, Masahiro Tomita and Yoshiaki Yamazaki and Yusuke Kashima for the translations. 00;01;31;14 - 00;01;47;21 So can you tell us about the origins of MyNA Like what inspired its creation and how has it grown over the years? 00;01;47;24 - 00;02;26;18 The origin of the MyNA is starting from the translation of MySQL reference manual, which will only exist in English and Tomita san translated into Japanese. It was October 1997. 00;02;26;20 - 00;03;05;00 Since after publishing translated version of reference manual got a number of inquiries coming into my private mailbox. 00;03;05;02 - 00;03;43;01 Then I felt like I should create a mailing list. So, it was in January 1998 Tomita san created a new mailing list. After a while there are, discussions going on. Then year 2000, the major members of a mailing list gather together to have a drink. Then they decided to take a domain name, mysql.gr.jp and also they formed a user group, name it iMySQLPeople Association or instead MyNA 00;03;43;05 - 00;04;09;07 Could you share some highlights from MyNA activities such as events, meetup or collaboration that came from the that Nippon user group? 00;04;27;26 - 00;04;55;00 Sakai san join the MySQL User group in 2003. It's already 20 plus years ago. Then the main purpose of the mailing list was exchanging ideas, asking questions, someone else to answer. The user group is focusing on, ease of use and use 00;04;55;02 - 00;05;22;17 of Japanese languages, as well as promoting product to the market and communication between users in Japan. 00;06;12;10 - 00;06;44;08 This was for all the user groups and also committee members using Japanese language in MySQL or or reading manuals written in Japanese. That's already pretty much done. And it. Also, everyone in Japan actually knows about MySQL. Well, so we're more focusing on the communication between users on MySQL and preparing the place to people to gather together, to communicate and exchange ideas each other. 00;06;44;10 - 00;07;16;19 Before Covid, we were occasionally running offsite events like meetups, but Covid prevented to run those events. Then we shifted to online. However, we found the offline event. It is a more, better option. People who can communicate freely and discussing, more. And we prefer offline events. Then we, terminated online ones. But earlier this year, we finally resumed offline meetups. 00;07;16;22 - 00;07;37;14 And if people gathered together face to face and having drinks, which was a really good event. 00;07;58;11 - 00;08;21;08 One more highlight of the user group activity is in collaboration with other conference. In Japan that are famous open-source focused event named Open-Source Conference in Japan. They are running all this running over ten cities or even towns in Japan. 00;08;21;12 - 00;08;52;06 And these events are running more than 20 years and nearly all major or even minor open-source communities and individual user groups are joining this event. MyNA MySQL user group in Japan is always, no exception. Always participating, dissident and communicate. Talking with people from other communities, introducing new stuff or learning from others. And it helps other people to understand the details of MySQL. 00;08;52;08 - 00;09;18;06 I would like to, to ask you one thing because of all this, to to see if, I'm right or not, but, I don't know, I don't understand Japanese had the chance to meet you guys, already? Several times. But, I see on social media sometimes. Also, MyNA kind of magazine or cover are there are they're publishing a magazine or something like that at all. 00;10;21;10 - 00;10;53;20 There are number of published publications by MySQL group members, and they're, individually writing blogs or, posting some articles to either print to the magazines or online magazines. 00;10;53;23 - 00;11;19;15 And there's a one book, which is a really famous book in Japan, written by user group members. And that's also all mentioning about a user group in a book, by the way , the book was published in 2000. And now or most recent version is the fourth edition of the same book, and it was one of the most popular MySQL book in Japan. 00;11;19;18 - 00;11;53;27 Also, on other online articles, about Mysql Written by the user group members again, and it's already counting over 230 times to articles, on the web. I think it's great that the the group members are so involved and they collaborated to actually write a book that's impressive. So what are some of the most exciting trends or innovations in MySQL that your members are discussing today? 00;12;27;07 - 00;12;58;13 One of my most favorite update around MySQL, operating recently is LTS. It's a long-term support which brings stability to the product as well as applications we develop. I agree the LTS is a great thing happening to MySQL. 00;14;06;05 - 00;14;35;12 My personal favorite feature on MySQL, which have a major update in the MySQL 8 is GIS. With MySQL 8.0. 00;14;35;15 - 00;15;06;09 GIS features now supports Geo tech system which makes it GIS more precisely accurate to visualize. So real world. My favorite part of this feature is his brings MySQL database to shows of data in the real world. And that, excites me is and we are I'm talking about this feature item during the event and the community events and so on. 00;15;06;11 - 00;15;43;17 The one thing I try to request is improving the features, enhance features of MySQL GIS. You guys to catch up was PostGIS which is a popular products in Japan. What can we do here? Probably of the world. So yeah, it's makes sense. And to be honest, I would just, recommend guys to just communicate and with me for example, because we did the same when we started with a GIS, we at Uber moving from Postgres to MySQL and, we implemented, stuff they needed first. 00;15;43;21 - 00;16;04;24 So they ask us so we, we collaborate with them. So if you be the same, we are open to, feature request. No worries. So if there is something you, you would like to see there, in the GIS, just, let us know, and, we will see what we can do. Because, yeah, the GIS, it's something that we improve a lot. 00;16;04;24 - 00;16;25;29 And, when people ask stuff, we can do it. So another reason that. So now I would like to ask that, if you're looking ahead, what are the MyNA and, next initiative or project that you have in the pipeline for next year because, as you know, I also, MySQL will, turn 30. 00;16;26;06 - 00;16;52;04 So will you do something special? And stuff like that? For that celebration? 00;17;14;14 - 00;17;38;02 We have not to finalize yet about what to do. But we are believing. 00;17;38;02 - 00;18;09;11 We gotta do something because the next year is the anniversary year of MyNA as well. It's a 25 years, so we really want to have something like a joint celebration anniversary, event with the MySQL team in Japan, as well as MyNA. MyNA seems to be a very popular, very active group. Probably a user group that can be used as a model for other user groups around the world. 00;18;09;13 - 00;18;38;01 What advice might you give someone interested in joining or starting a similar group in their own region? 00;19;38;13 - 00;20;09;11 One one thing we are always keeping in our mind is we do whatever we want. But we don't have to push. We do not push us too much. Because to run user group, keeping user group running is the highest priority. But it is nothing easy. So if you force to someone else to do or force yourself to do something, it's not easy to continue to be relaxed. 00;20;09;14 - 00;20;37;26 And another important thing is generating the place to people gather together. It can be online, can be offline. But once you prepare a place and you you can invite a people. People will come and they will invite other people as well. And the user group is not really. The place someone to teach someone else. It's more like place to gather together, having a chat, communicating. 00;20;37;29 - 00;21;12;03 That's a user group, we believe. And what we're saying is we always eat, not again. Be relaxed and don't be stressed. Do what you want. That's or wouldn't be otherwise. But that's how we keep this user group running for more than 20 years. Excellent. Very nice advice because, we know that, the Japanese user group is maybe one of the biggest, or at least the most active, for MySQL. 00;21;12;03 - 00;21;31;21 So it's a it's very good. Thank you very much. That's a wrap on this episode of Inside MySQL: Sakila Speaks. Thanks for hanging out with us. If you enjoyed listening, please click subscribe to get all the latest episodes. We would also love your reviews and ratings on your podcast app. Be sure to join us for the next episode of inside MySQL Killer Speaks.
/episode/index/show/d0cd255f-ccaf-4b55-a7da-5825f8230161/id/34887590
info_outline
MySQL Time Capsule
12/13/2024
MySQL Time Capsule
In this episode, Fred & Scott share their history with MySQL - including when they first started using MySQL and discuss some of their favorite features. --------------------------------------------------------- Episode Transcript: 00;00;08;15 - 00;00;30;23 Welcome to Inside MySQL Sakila speaks - a podcast dedicated to all things MySQL. We bring you the latest news from the MySQL team, MySQL product updates and insightful interviews with members of the MySQL community. Sit back and enjoy as your hosts bring you the latest updates on your favorite open-source database. Let's get started. 00;00;30;29 - 00;00;56;13 Welcome to Inside MySQL: Sakila Speaks, I am leFred and I'm Scott Stroz. Hi, Scott. So today we start the season two first episode. Am I right? Indeed. And unlike previous episodes, it's just you and me. We don't have a guest. We're going to talk about our experiences using MySQL That's awesome. So, Scott, tell me, how do you came to MySQL and when was it? 00;00;56;20 - 00;01;30;28 I know it was in either late 2001 or early 2002. I had just started a job as a web developer for the company I worked for as a paramedic, previously. So, I switched careers, but I was fortunate enough to stay at the same company and I had no budget. I was I literally had to create. I literally had to build a server out of spare parts in the back room, and I used a LAMP configuration. 00;01;30;28 - 00;01;56;07 So, Linux, Apache, MySQL and PHP, and if I remember correctly, the first version was 3.23 I think was the first version that I used, and I've been using it ever since. I've done most of the work I've done with MySQL has been on personal projects, so any time I've had a little personal project I've done, I've used that. 00;01;56;07 - 00;02;26;14 And there's been a couple of projects, you know, from jobs that I've done, you know, pretty big jobs for like big government agencies that have used it as well. How about you? For me, I was expecting you had started before me, so I would have looked younger, but so I started. But with MySQL the first time I really discovered MySQL without really knowing what it for. 00;02;26;17 - 00;02;57;00 I was already 1997 because I was a fan of Linux and still I am right there. I may be one of the only guys who, before 2000 went to a Linux desktop. Even so, a Linux desktop year was for me a long time ago. And so I remember it's a fun story because I went to a computer shop to buy some games. 00;02;57;03 - 00;03;23;17 I wanted to buy a game, in fact, and the game was just the small floppy disk and it costs and at that time I think it was around what we call thousand Belgium franc before Euro. So, and, and there was this box of five or six CDs called InfoMagic CDs where it was Linux on it. Right. 00;03;23;19 - 00;04;05;07 And and this is I say with the same money I would have more with than a floppy, I will have a full CDs there. And so this is how I started to install the first time Linux on my machine. And it was a bit before 1997, the first InfoMagic. I think it was around 1994 or five, but it was without MySQL at that tie and every year I was buying the new InfoMagic set and there was MySQL 3.20 in beta – in slackware - at the time and this is so I install it the first time and then I started to try to have a look at it. 00;04;05;09 - 00;04;33;03 and as I was doing computing at a computer science job and it was a time of CGI in Perl, I remember I started with something called Sprite and that allows you to write and to SQL on flat the text file. So we were using that to record the, the IP of people visiting to read, counters not to not incremental the day. 00;04;33;06 - 00;05;07;18 And then I switched to MySQL to do that, to have something even better than a flat file. But this was just during the study I would sit and after death, professionally, I met MySQL already around between 2002 to 2004, I guess, and the company I was working in Belgium, we started to work with MySQL AB at the time and I passed the training in 2005. 00;05;07;18 - 00;05;38;01 It was still in MySQL 4.1 exams at the time and we had the core and professional exam and this is how I really jumped in MySQL as a daily work, I would say taking the exam and then doing consulting in Belgium for MySQL. And after that I also worked with the make company, the one I was working for with MySQL AB to provide also training so for MySQL. 00;05;38;01 - 00;05;59;25 So the the usual training of MySQL AB or as some companies in Belgium were basically to be was not able to deliver because there were too many people they wanted in some time in French and Italian at the same time. So it was a bit and this is how I really started to learn and study MySQL. So I really enjoyed that. 00;05;59;27 - 00;06;36;21 But I never end up there. It was this fast, always move forward both. As you know, we also do a conference. You do? We do conferences. I do talks and I really jumped into MySQL community. Meaning then let's hear meeting all these stars of MySQL and stuff in 2010 when I gave my first talk at FOSDEM. 00;06;36;23 - 00;07;02;01 So this was about maintaining too big tables in MySQL. And because I was maintaining big budget business in companies in Belgium, all in MySQL, MySQL was everywhere. So that was very good. And so I go there and this is where I met a lot of people and the community manager at the time in MySQL and plenty of other people. 00;07;02;07 - 00;07;47;04 And this is all I really started jumping in the community of MySQL. For the longest time. I was kind of like a lurker in the community. I didn't really post a lot of questions or answer a lot of questions on the forums, but I spent a lot of time there learning stuff. So, I, like I said, I've been using MySQL for over 20 years now and one of the things I use it for and I've talked about this before in presentations that I've done and I may have even mentioned it on the past episodes, but I manage a golf league, and the golf League grew to the point where we couldn't really like we 00;07;47;04 - 00;08;07;26 used to track everything in an Excel spreadsheet and we couldn't do that anymore because we actually had - we we've grown to 80 golfers. There's 80 golfers in the league. We have 40 that play in one night, 40 that play in another night. And I wrote a web application to help me manage the golf league. I can do scheduling. 00;08;07;28 - 00;08;29;13 There are guys who are responsible for entering the scores, so it tracks people’s scores a calculates their handicaps. It figures out who is in the lead. Okay. And one of the things that used to drive me crazy was I have a stats page where you can look up your stats, you can look up you know, what you've shot in previous rounds. 00;08;29;16 - 00;08;49;28 Which holes do you shoot the better, better on as compared to others. And then it it counts the number of birdies, pars, whatever that you have it gives you a percentage. But it also compares it to everybody else in the league. So, you know, you can say, hey, I birdied 10% of the holes, but the league’s birdied 15%. 00;08;50;01 - 00;09;12;15 And some of those queries used to take a long time and I it wasn't like a ridiculously long wasn't like people were waiting for like minutes for the stats to come up, but it was longer than I thought it should have. And I realized that the solution to that problem was going to be setting up a query that uses common table expressions. 00;09;12;17 - 00;09;42;16 But unfortunately at the time MySQL did not support it and that when I forget what version it was that that CTEs were introduced. But I switched over like immediately, like I got my development environment, I created the queries the way I wanted them. They were actually orders of magnitude faster than what they were. And I was like, Wow, this is like the greatest thing since pockets like that were. 00;09;42;16 - 00;10;07;23 To me, that was like a huge, like change in, in my development attitude of, you know, we have, you know, basically, you know, common table expressions, are kind of pre aggregating data a little bit. And I was like, wow. I, I had them in just one particular place. And I've actually changed a bunch of queries since then to use them because I'm like, wait, I can speed this query up. 00;10;07;25 - 00;10;38;17 And again, it's not the website doesn't get so much traffic where people are going to notice these things. But I noticed that I like I'm like, no this could be faster. And I think for me, for this particular project, adding CTEs was probably the best feature we've added because for me in this particular instance, it added a lot of value to helping speed up queries that were otherwise not very efficient. 00;10;38;19 - 00;11;13;27 Is there something like that for you? So this was MySQL 8. It's what was very what we always say, a big giant leap for a SQL in the most critical system. Right? So MySQL at all this knew I would say new for MySQL features like a windows expression, common table expressions and so on. So just to so on the team, you are the developer guy, so the guy will use MySQL as a developer and the guy more in the sysadmin, DBA path. 00;11;14;02 - 00;11;49;19 So for me, yeah, it's cool to have CTE and Windows function but this is not what for me was a shining for me was an issue on the other side or lower side. Something that for me was like, this is so great. It's for example, the clone plug in, clone plug in. It's amazing when you have to deploy databases because I had to manage the database, not writing the code or sometimes when people were writing code into something better could say, look, we are doing full table scan, please fix this. 00;11;49;21 - 00;12;25;01 And if I knew, I would explain how to fix it. But so this is yeah, all I do. It's a clone. And after that, plenty of other stuff was really what we were looking for in, in MySQL for the operation part. So cloning data, not having to take a back restore through to do the point in time recovery, replay the binary locks and also and all that was really what we I was expecting. 00;12;25;05 - 00;13;00;27 So I will I love this and everything around to MySQL Shell and Admin API. So to create replication create clusters so easily with what we saw in Season One with Miguel, this is what really for me was the two most advanced stuff in MySQL8.0. Yeah, I've become a huge fan of MySQL shell. Like it's I, I for years I used to shy away from like command line interfaces mostly because I'm a very poor typist. 00;13;01;00 - 00;13;30;01 And so for a lot of stuff I would use Workbench and I would say over the last three or four years you could probably count on one hand the number of times I've opened Workbench because I just use Shell because like you said, there's there's so much stuff that you can do. It's like, I mean, you could spend weeks just exploring new features and how to use them and how to implement some of the stuff that we have in Shell and still have new stuff that you're like, I didn't know we could do that. 00;13;30;04 - 00;13;59;07 Yeah, MySQL Shell and the team is very dynamic out of it, so they do plenty stuff is also the MySQL Shell now included in Visual Studio Code. So but I am a terminal guy. So for me the most well, the MySQL Shell standard one terminal is the one I prefer, right? Like you, Workbench. I could use it only maybe two or three times in my entire career. 00;13;59;09 - 00;14;32;03 So I really like command lines. But yeah, it's really, really nice or what we can do. And we did. So it's very, very nice. And so yeah, is something we also we need to say because it will happen soon. Now and because we are using it for a long, long time. And don't forget that next year will be something a very nice milestone for for MySQL, right? 00;14;32;10 - 00;14;59;25 That's right. We'll be celebrating 30 years of MySQL which is pretty pretty impressive for open-source software I think. Yeah I it's wonderful and very happy and yeah, I've been part of, and you too, of that longer journey at 30 years we did. So I am very proud of that and I think it's very, very nice. 00;14;59;28 - 00;15;27;13 So yeah, I think we MySQL evolved a lot since the beginning of course, and we keep involving now with everything we see, but we will talk to that in future episode I guess, right? That's right. I will say that the, the recent news is the availability of HeatWave MySQL in Oracle cloud as part of the always free tier that's that's very nice. 00;15;27;17 - 00;16;03;11 I actually move the database from the golf league application to HeatWave MySQL on the day it was available. Like the day we found out, okay, it's out there. It's lot. It's live. I switched the database over because I was think I was waiting for like I had prepped. You know, I did the the dry run with Shell to say, you know, to do a dump and be like, you know, the OCIMDS set to true and it let me know all the problems I had which there was only if I remember if there's only four issues that were there HeatWave is so it's amazing plenty of feature and it's true 00;16;03;11 - 00;16;30;10 that some people who are a bit did you don't know what to expect about it just just see the the videos or they saw our presentation but now they can play with it for free and and all use it all always free. So this is amazing that with the always free compute instance you can put everything in OCI for free to start with to learn it. 00;16;30;12 - 00;17;07;01 This is a quite amazing too and there is plenty of stuff. There are also very, very interesting course, as we all know, a cloud is also part of the what people are doing now. So people like to move to the cloud and so mostly it's a very nice a contender too, if you want to have your most well, your your database in the cloud, the strength of MySQL HeatWave, if all they're running to MySQL, is that it's the most accredited support team and the MySQL team who makes it and this is amazing. 00;17;07;01 - 00;17;36;22 I see you we can see the difference if people see the difference by both. This is the MySQL guy managing my database. So that's this is cool, right? And the other thing that I like is with Heatwave MySQL, it's actually based on the enterprise version. So for in the always free tier you actually get enterprise features such as being able to create stored functions, stored procedures in JavaScript, the data masking and some of the other enhanced security and as well as some of the enhanced performance. 00;17;36;24 - 00;18;03;27 So those are things it's to me it's really cool that you can we can have those things, try them out for free, or if you have a just even a small application like the one that I work on, you know, I have I've been using Oracle for hosting for years and I haven't paid a penny for it. And now I have, you know, my my database running in Heatwave MySQLand again as part of the always free tier I'm not going to pay anything going forward either. 00;18;03;29 - 00;18;29;19 You know that's that's great. We have a very great news now we were expecting that always free you or MySQL heatwave so now it's there so I'm going to wait for all your nice MySQL short content about it and the so thing we reached the end of this episode so thank you very much Scott Thank you Fred Thank you for listening. 00;18;29;19 - 00;18;47;01 Bye bye. That's a wrap on this episode of Inside MySQL: Sakila Speaks. Thanks for hanging out with us. If you enjoyed listening, please click subscribe to get all the latest episodes. We would also love your reviews and ratings on your podcast app. Be sure to join us for the next episode of Inside MySQL: Sakila Speaks.
/episode/index/show/d0cd255f-ccaf-4b55-a7da-5825f8230161/id/34432255
info_outline
MySQL 8.4 LTS: A Balancing Innovation and Stability
06/25/2024
MySQL 8.4 LTS: A Balancing Innovation and Stability
Fred and Scott are joined by Mughees Minhas, Product Management Senior Vice President of Enterprise and Cloud Manageability for an informative discussion of the latest LTS release fo MySQL and how the new versioning of MySQL provides a balance of innovation and stability. -------------------------------------------------------- Episode Transcript: 00;00;00;00 - 00;00;31;20 Welcome to Inside MySQL: Sakila Speaks, a podcast dedicated to all things MySQL. We bring you the latest news from the MySQL team, MySQL product updates and insightful interviews with members of the MySQL community. Sit back and enjoy as your hosts bring you the latest updates on your favorite open-source database. Let's get started. 00;00;31;26 - 00;01;00;22 Welcome to Inside MySQL: Sakila Speaks. I am leFred. and I'm Scott Stroz. Today's episode is related to the implication of MySQL introducing LTS and to talk with us, we are joined by Mughees Minas. Mughees is the senior vice president of Product Management and Marketing, Enterprise and Cloud Manageability at Oracle. With over 20 years of experience, he has been instrumental in developing some of the most widely used Oracle Database Technologies. 00;01;00;24 - 00;01;31;26 Currently is working on MySQL HeatWave, the next generation of cloud databases. Welcome, Mughees Hi, Fred and Scott. Nice to be here. Thank you for joining us. So, how does the introduction of MySQL 8.4 as the ELTs impact the stability and long-term support expectations for businesses and developers relying on MySQL. Well, first of all, let me say that, you know, these changes that we have brought, it really is a response to what our customers have been telling us. 00;01;31;28 - 00;02;04;00 So, the first thing I will say is that, yes, we do listen to our customers. Just to give you a little bit of a background. The patch releases of MySQL 5.7 and releases prior to that were focused on bug fixes and security patches. But that changed in 8.0 where we adopted this continuous delivery model in that patch releases not only contain bug fixes but also new features. 00;02;04;02 - 00;02;30;10 So that was good for a number of our customers because it allowed us to release new features more frequently rather than having our customers to wait for a couple of years before they can get new features. However, there's also a downside to it because there are certain customers who really want a stability and this approach of continuous delivery was causing challenges for them, for projects and applications that required stability more. 00;02;30;10 - 00;02;51;26 They were only interested in critical bug fixes and patches and they did not want behavioral changes. So anyway, so we've listened to the feedback. We've looked at industry trends and we've now transitioned to a versioning model which allows us to do both. It allows us to have an innovation track and an LTS or long-term support release track. 00;02;51;26 - 00;03;16;01 So, the first thing I would say is that we introduced our first LTS release last month - 8.4 and with this new model, our customers who want stability. They want only critical bug fixes, security fixes and so on. They can adopt the LTS version, which came out, as I said last month. And those who are interested in new features because maybe they ask for those specific ones. 00;03;16;04 - 00;03;53;11 We also had this innovation train that they can adopt where with every patch that they will get the latest features that we are working on. So, our goal is really to ensure that the MySQL community has an exceptional user experience with both our innovation releases as well as are LTS long term support releases. In what ways does the LTS designation for MySQL 8.4 influence decisions around migration strategies and adoption timelines for organizations who are already using MySQL or might be considering switching to MySQL? 00;03;53;13 - 00;04;17;20 So, as I said earlier, MySQL 8.4 is our first LTS release and this one is focused on stability and bugfixes. The next innovation release will be 9.x - 9.0 - , which will have new features straight and after two years of innovation releases. We will have the next LTS release will be 9.7, which will come out, as I said, two years from now. 00;04;17;23 - 00;04;48;07 And as you can see, the way the numbering works is that we'll have a release every quarter. So ,you start with 9.0 after eight quarters we are you will get to 9.7 and that becomes our next LTS release. So, the thing about consideration that on migrations and upgrading and downgrading something for the customers to be aware of is that within an LTS release, the functionality remains the same and data format does not change. 00;04;48;11 - 00;05;11;08 Therefore, we support in-place upgrades and downgrades will be possible within the LTS release InnoDB Clone will be supported with an LTS release both for upgrading and downgrading. So, in this one, LTS gives you enormous advantages when using, upgrading and downgrading. And these are some of the considerations people have to have when they're looking at migration, upgrade and downgrade and so on. 00;05;11;10 - 00;05;46;29 So, with MySQL 8.4 LTS Right. What new opportunities will emerge for third party developers and service providers to enhance and extend that the MYSQL ecosystem? I'll just reiterate the fact that both LTS and the innovation train are GA production grade production quality and fully supported. All right. So, it's not as if we are taking any shortcuts in terms of release quality when we do innovation releases versus LTS release. 00;05;47;01 - 00;06;06;10 We do the very best we can do in terms of testing, quality assessment and so on. But, you know, anytime you a new code, it's just a fact of life. There are certain things that happen that we don't catch in our testing phase, and they do introduce instability. It's just a fact of life when it comes to new software development. 00;06;06;12 - 00;06;33;16 Having said that, when to use innovation releases, when to use LTS releases, it's up to the customer. But I can see that for those who want to access the latest features and improvements and enjoy staying on top of the latest technology innovation release is what they want. Oftentimes, these are ideal for developers and DBAs who work in a fast-developing environment. 00;06;33;19 - 00;06;57;08 They are trying to build a brand-new application. They want to take advantage of the latest features that the industry has to offer. And so, they would be very interested in doing that application development on innovation releases. And once they have built the application, they're looking for stability. Then they can adopt the next LTS release that comes with that innovation release for stability phase. 00;06;57;08 - 00;07;17;02 But I think for new application development, they there will be a lot of interest in doing it on the innovation releases. Also, if they have an interaction with us in product management and we hear from a customer, they want certain features. If you build a certain feature for them, the way they introduce it to them is through innovation release. 00;07;17;07 - 00;07;44;14 So anyways, we see that is something that's very useful for our new application development by developers. Now when to use the LTS release? Well, when you have an application where you require stability you these releases only contain necessary fixes. There is no change that breaks anything. And you basically have an application that's running fine. Your job essentially is to make sure your users use it. 00;07;44;16 - 00;08;05;19 Quality of experience is good, their application issue and so on and so forth. The application itself is not changing dramatically, right, Because it's the same application. Maybe you just upgraded to the next version and so on. And in this kind of situations, the LTS released the very appropriate. When there is less application development sort of things going on and stability is the key factor. 00;08;05;21 - 00;08;35;11 So once again, even on both MySQL, on premises as well as on the cloud side, we offer – in the heat wave that is - MySQL HeatWave. We offer both innovation and LTS release options. This model will be available both in the cloud as well as on premises. So how, how do you think the maintainers of popular open-source projects like WordPress and Drupal will change their development process with the new LTS versioning? 00;08;35;13 - 00;09;10;00 And do you think that maybe they might plan to integrate the innovation releases into their development tree? So, it's a little bit of speculation on our part. You know, first of all, most open-source products do have a similar innovation versus LTS release model. So, it's not as we're not the inventors of this, people know about that. But what I expect is that companies like WordPress or Drupal and so on, they will not be able to choose the LTS for the stable versions and the innovation releases, the innovation train or the under-development releases. 00;09;10;03 - 00;09;32;16 So, we look forward to working with our open-source products to improve the MySQL roadmap, the innovation release phase. So, this really allows us to use the innovation train as a way of addressing their requirements for us. So, we can if they ask us to add a feature, we can do that. So, they would use the innovation train for application or under-development releases. 00;09;32;19 - 00;10;13;06 But once they actually go out and make them production, we like expect them to use – rely more on the LTS release. So, I think it'll you'll see a combination of both of those things facilitating our third-party partners like WordPress and Drupal and so and so forth, how they will utilize these two releases in my opinion. So as a product management senior Vice President overseeing all of MySQL development, what features and performance and instruments of the upcoming MySQL 9 because you said earlier that the next one will be 9.0 are you the most excited about? 00;10;13;12 - 00;10;33;24 And is there a particular new feature or improvement that you can discuss with us that you feel that will be a very good for the MySQL community? I won’t list a specific feature, but let me just tell you directionally what we are trying to do in 9.0 release that I think is the part that excites me the most. 00;10;33;24 - 00;11;11;05 I think that is some of the stuff you've already heard about Gen AI integration. You know, as the vector search searches and vector store inside MySQL and so on, you know, you can really build great generic applications using MySQL. The other thing that we also plan to do in 9.0 is to use AI and AI models to simplify, demystify makes easy managing and monitoring of large sets of MySQL instances. 00;11;11;08 - 00;11;48;13 We think AI offers us a great model where we can use machine learning and these kind of algorithms to identify behavior anomalies inside your MySQL databases. So instead of you encountering a problem reporting it - users reporting the problem, then you're taking action to fix it. We really are trying to use AI in such a way such that we can identify proactively issues and areas of failure to might encounter address them before your end users are impacted. 00;11;48;15 - 00;12;17;24 So, I think AI is not just about building new AI applications in MySQL, which we will, which we are doing, and we've talked about that already in different forums, but we also want to use AI to make your MySQL databases more stable, easier to manage, and your application behavior being more predictable and less problematic. So that is another part I think that we are working on. 00;12;17;24 - 00;12;49;00 We have built-in, we collect enormous amounts of telemetry on your MySQL instances. We collect metrics, we collect traces, we collect logs, we collect events and so on and so forth. And we then essentially run large AI algorithms on the set of telemetry that we have to not only tell you what's going on right now, but to see if we can identify sequences and patterns that is indicative of a problem that will happen. 00;12;49;03 - 00;13;17;21 So anyway, this sort of new I can't be very specific about what will come, this is really something that things like AI and ML allow us to do now, that was probably not as possible, let's say two or three years ago. So, I think it's been a very interesting phase and I think you'll see more and more of that coming from our side as well, that we will use AI to tackle it things at both ends to make your experience of my skill more seamless, superior using AI. 00;13;17;28 - 00;13;47;09 And also, you can build apps on MySQL as well. So, the I think you'll hear a lot more about that. And this is some of the things that I think 9.0 release will have, and I'm working very earnestly on this and we think it'll be a pretty cool set of features that be released. Thank you very much for joining us, Mughees, in this episode about the implication of MySQL introducing the long-term support release – 8.4 the first ever LTs version of MySQL 00;13;47;09 - 00;14;06;19 So, thank you very much. Thank you. My pleasure. Thank you Mughees. That's a wrap on this episode of Inside MySQL: Sakila Speaks. Thanks for hanging out with us. If you enjoyed listening, please click subscribe to get all the latest episodes. We would also love your reviews and ratings on your podcast app. Be sure to join us for the next episode of Inside MySQL Sakila Speaks.
/episode/index/show/d0cd255f-ccaf-4b55-a7da-5825f8230161/id/31883367
info_outline
Mastering MySQL Group Replication
05/28/2024
Mastering MySQL Group Replication
Luis Soares, Senior Software Development Director and the "face" of all things MySQL replication, drops by to enlighten us about group replication and its different uses in the MySQL ecosystem. --------------------------------------------------------- Episode Transcript: http://insidemysql.libsyn.com/mastering-mysql-group-replication Mastering MySQL Group Replication 00;00;00;00 - 00;00;31;20 Welcome to Inside MySQL: Sakila Speaks, a podcast dedicated to all things MySQL. We bring you the latest news from the MySQL team, MySQL product updates, and insightful interviews with members of the MySQL community. Sit back and enjoy as your hosts bring you the latest updates on your favorite open-source database. Let's get started. 00;00;31;23 - 00;00;58;27 Welcome to Inside MySQL: Sakila Speaks. I'm leFred and I'm Scott Stroz. Today we are joined by Luis Soares. Hi, Luis. Hello. Hi. So, you are the MySQL replication team lead. You are responsible for the MySQL binary Logs replication related code base and MySQL bin lock tool. Yeah, that's correct. I'm happy to lead a bunch of very great people, very knowledgeable people. 00;00;58;27 - 00;01;22;22 So that thing comes easy. So, we all know you as the face of all things application in MySQL and this is why you are also the responsible of HA, point in time recovery and channels in MySQL HeatWave. So, for HA, we decided to eat our own dog food and am I correct HA in MySQL HeatWave is also using group replication isn't it? 00;01;22;24 - 00;01;52;10 Yeah. So along with the other OCI technology, we use group replication under the hood to build the fault tolerant DB system in in the MySQL HeatWave database service when deployed in single primary mode. By the way, a "DB System” for those that are wondering what it is it's the abstraction that captures all these things that are managed by the service on behalf of the user. 00;01;52;12 - 00;02;22;19 Like setting up replication, keeping everything running perfectly fine. Orchestration, orchestrating all these things related to backups and so on and so forth. In terms of how businesses can benefit, what are some of the benefits of using group replication. In the MySQL HeatWave services, there's the DB system. That's what users relate to. And under the hood we have group replication to provide fault full tolerance, right? 00;02;22;21 - 00;02;51;09 Group replication at its core relies on a quorum to commit a transaction and therefore if the primary server fails within the cluster, there is this guarantee that it's if there is a survive, there's a majority surviving this failure event, then the changes that have been produced so far will continue to be in the cluster, right? So, in other words, the data is preserved. 00;02;51;12 - 00;03;34;13 If there is a surviving majority in the event of a failure. The act of switching over the application when a failure happens is also relatively fast, because if there's a failure, there's a standby in the cluster ready to take over. So, we call that a secondary. So, usually, the time is relatively fast. So just for clarification, when you say as long as a majority of the nodes are unaffected, so you're saying like if there is a 5 node cluster and two of the nodes go down, then the transaction is still going to be committed, correct? 00;03;34;15 - 00;04;05;27 Yeah. In group replication, it happens like that, right? As long as you have the majority surviving the failure, the change will be carried on forward. Right. In which case in the MySQL HeatWave service clusters typically have three nodes primary and two secondaries. And so that's how it works. I think also it's because as we are operating this, when we have one failure, our guys can jump in directly and fix everything. 00;04;05;27 - 00;04;31;13 So, we don't need to have too many nodes there either, I guess, right? Yeah, it's I think so. It's a combination of automation and sometimes manual work. Right. So, since your team Luis is operating all the clusters in MySQL HeatWave service did group application got some improvement related to that? Yeah. I mean over the years group replication has been always evolving, right? 00;04;31;13 - 00;05;20;28 And with this with a need to power a cloud service, of course group application had to be...well it had to keep up with that right with that task or with the requirements for that task. And therefore there's has been a lot of enhancements to observability, especially with, especially with memory, more memory, implementation. So, I think over the years, if you look back into what are the replication performance schema tables, what are the replication related stages, variables and so on, you'll see an increase of, of things that have been instrumented and exposed through new columns in performance schema tables or new stages variables. 00;05;20;28 - 00;05;51;10 That's these things are extremely useful when you're when you're running things at scale. So, you need to observe to understand what exactly is going on, how, how exactly to operate and intervene in the system. So, the self-serve ability is paramount. Right? Moreover, we've been making group replication more efficient, making it more resilient to cope with that with the different types of failures. 00;05;51;10 - 00;06;25;00 Some of them are edge cases, but they happen. Also be able to deal in a more graceful way with slow instances so that it doesn't affect so much the overall state of the cluster. And we we've also extended the GR to be able to automatically recover from a few edge cases too. So, this is a whole plethora of, you know, new things that have been happening in GR over the years. 00;06;25;02 - 00;06;58;09 Yeah. And we can also say that by improving group replication for HeatWave HA right, you are also improving group replication in general. And then for example, InnoDB cluster benefits from that too, which is very great for everybody. Yeah. I think you can say that. Yeah. When I think of replication I think of making sure that the data is actually, to be redundant, replicated to a different server, to serve as a backup, read replica or something along those lines. 00;06;58;11 - 00;07;37;12 But how else can we use replication in MySQL HeatWave database service? Let me start by saying that MySQL replication has a lot of different uses in traditionally within the MySQL context, right? So, replication is or can be used for implementing things like high availability, things like read scale out by replicating for many different servers and then reading from these servers and therefore offloading the read load from the primary server. 00;07;37;17 - 00;08;07;26 So, it can also be used for and for things like point-in-time restoring particular by leveraging the binary log and even some sort of change data captured by mining the binary log which itself is a log that captures deltas or changes to your data over time. So in the MySQL HeatWave service, we follow more or less the same pattern, right? 00;08;07;28 - 00;08;42;14 We use, like I said before, from a on a previous question, we use group replication to implement fault tolerant DB systems by having redundant servers and therefore if there is a failure we can fail over from the failed server to 1 of the secondaries. But we also use replication for things like replicating from on premise to the MySQL HeatWave service and vice versa. 00;08;42;14 - 00;09;17;02 Right. So, it's this is what we typically call inbound and outbound, respectively. Some of the use cases are for things like live migrations or for setting up hybrid setups. If you couple that together with replication filters, you can even do things like partial replication from one place to another and just, you know, just having parts of the data in, for instance, an on premise and parts of the data on. 00;09;17;02 - 00;09;43;04 MHS right. So, this allows this is a very flexible, a very flexible tool, if you will, to do these types of setups, as well. Like a like I mentioned, I mentioned before, the binary log that can be used for point-in-time restore. We also use it for point-in-time restore that in the cloud, too. 00;09;43;04 - 00;10;29;25 So, replication as a whole is present everywhere in the MySQL HeatWave Service. Thank you Luisa I saw as you said, you were talking about filters that we have integrated in MySQL HeatWave. Because you said we can migrate from on prem to HeatWave. But we have also I have also seen that we can migrate from to cloud to MySQL HeatWave in OCI and we have predefined or the team has predefined some features to migrate from non-vanilla MySQL so from Amazon or whatever to our own cloud very easily for the users. 00;10;29;25 - 00;11;18;00 Right now there's a few things that when you when you replicate from an external source anything can come down the replication pipe and anything can that comes to down the replication pipe might be conflicting what with what you're running on your target instance. So, you mentioned other types of but well how to call it you mentioned some other maybe cloud providers or something that can have their own modified syntax of commands that are executed against their own, their own versions of MySQL 00;11;18;00 - 00;11;45;05 All these things, of course, can have or cannot be applied on a vanilla maestro and therefore need to be filtered out. So, this is the type of thing that these filters can help you with to avoid this, corner cases or this specific cases where you have incompatible traffic coming down the pipe and you would like to avoid it without breaking replication right. 00;11;45;07 - 00;12;24;06 So that's about it. So, thank you very much, Luis. So, keep improving HA, keep improving MySQL HeatWave high availability and in the same way everything replication yInnoDB cluster replica set, cluster set all that as a replication on the route so it's it's cool and everybody likes it. This is why MySQL are still very known for this replication. I would like to say one thing before we close... we talked about replication as if it's a cool new thing and so on. 00;12;24;06 - 00;13;03;16 But it's it's interesting it's very interesting that within my MySQL itself, has traditionally been around with the with MySQL for a very long time that, right. So, it's very interesting how things have evolved over the years and continue to evolve right. Like, Fred you were saying let's continue to improve it let's it's everywhere and so on and so forth. So, it's a very interesting thing to observe over the years seeing these this gradual evolving of replication itself. 00;13;03;18 - 00;13;23;24 It's nothing new in my spell but it's been evolving so much over the years and it's very, very interesting from I mean, I'm biased but from where I stand it's a great thing to observe, I think. Thank you, Luis. That's a wrap on this episode of Inside MySQL: Sakila Speaks. Thanks for hanging out with us. 00;13;23;29 - 00;13;47;04 If you enjoyed listening, please click subscribe to get all the latest episodes. We would also love your reviews and ratings on your podcast app. Be sure to join us for the next episode of Inside MySQL: Sakila Speaks.
/episode/index/show/d0cd255f-ccaf-4b55-a7da-5825f8230161/id/31497197
info_outline
MySQL Shell Does All The Things!
05/07/2024
MySQL Shell Does All The Things!
For this episode, Fred and Scott are joined by Miguel Araujo, Senior Principal Software Engineer for MySQL Shell. Miguel outlines MySQL Shell's history and discusses its more popular and powerful features. The conversation winds down with us discussing our favorite features. --------------------------------------------------------- Episode Transcript: 00;00;09;13 - 00;00;30;16 Welcome to Inside MySQL: Sakila Speaks, a podcast dedicated to all things MySQL. We bring you the latest news from the MySQL team, MySQL product updates and insightful interviews with members of the MySQL community. Sit back and enjoy as your hosts bring you the latest updates on your favorite open-source database. Let's get started. 00;00;30;20 - 00;01;01;11 Hello and welcome to Sakila Speaks, the podcast dedicated to MySQL. I'm leFred and I'm Scott Stroz. I know today's guest for a long time already has had the chance to work with them on several solutions. Please welcome Miguel Araujo, Senior Principal software Engineer on the MySQL Shell Team. Miguel is the technical lead developer of the Admin API, core component of the HA and the replication solutions like the MySQL InnoDB Cluster MySQL InnoDB replica set and MYSQL InnoDB cluster set. 00;01;01;28 - 00;01;25;07 Welcome, Miguel. Hey guys. Thanks for inviting me to this podcast. So, Miguel, we want you to talk about MySQL Shell. Can you give us a high-altitude overview of what MySQL Shell is? Basically, what it is, who should be using it and why? So first and foremost, Shell is the command client for my SQL Server, right? 00;01;25;21 - 00;01;50;28 You can do with Shell what you could do with a classic MySQL client. So, you connect to a server to my SQL server and it can run queries on it using SQL. But Shell is much, much more than that. It's a... we like to call it a modern advanced command client for MySQL server, and maybe I should get a little quick history lesson about it. 00;01;50;28 - 00;02;27;00 So, Shell came out with... there was a purpose to build this new command client and this kick comes back to 2016. If I recall correctly, when the document store was being developed and implemented. And with MySQL Doc Strore we have created this new API to interact with it, the X-dev API, and this X-Dev API follow the common standards and this was implemented in JavaScript in Python, and for that we needed a new shell, a new command line client to interact with the server and speak. 00;02;27;10 - 00;03;05;16 This is new API and interact with the Doc Store. So, for that we create this shell with the with implementation of the X-Dev API exposed in JavaScript and Python. So Shell was born with a with this multi-language support so SQL classic and then JavaScript in Python and in the beginning with with the X-Dev API exposed to those two languages. But we also built it as a modern interface, so it has a customizable and reactive prompt. 00;03;05;29 - 00;03;32;21 It has auto-completion, syntax highlight. It has a built-in help system. So, it's built as the for example, we have in Linux bash or the Shell or on Shell or whatever or in Windows PowerShell and Shell can be seen as something like that. But for MySQL, so you started your shell, you can run commands in it, you can connect to instances and operate on them. 00;03;32;21 - 00;04;06;21 So, it has this interact interface and also a scripting interface because since you have support for those languages, for JavaScript Python and SQL you can write your own scripts and then you can execute them in in Shell. And a another general feature ... most known and, and useful are the APIs built in. So I was just mentioning the X-Dev API that was the first one. 00;04;07;07 - 00;04;37;05 And then we of we have introduced the Shell API and the utilities and then the Admin API and the so starting with the Shell API, for example, we have operating system utilities. You can create reports, you can create plugins. The utilities include things such as the upgrade checker that is a utility built in shell that you can use to verify whether your server is ready to be upgraded to the new version. 00;04;37;20 - 00;05;09;05 And if not, what needs to be done. You have things as dump and load to dump instances and load them. This is very fast. It's it's very loved by the community and the Admin API that is used to deploy MySQL architectures like Fred said in the beginning – InnoDB cluster states replica set and so on. And also Shell is extensible, can write plugins for it and that's something great. 00;05;09;05 - 00;05;35;10 And that's one of the things that makes it a modern client. Yeah, to be honest, I am a very fan of Shell. It replaced the old MySQL client for me, the classic one I always use Shell everywhere. And so recently during the MySQL Belgium days, who you are there, you were speaking also about Shell. Many people like Booking.com and Canonical guys. 00;05;35;18 - 00;05;58;14 They praised MySQL shell. They use it, they love it, and especially the admin API. So let me ask you a personal question. As the Admin API is your baby, are you proud of that? Oh yeah, I am. And it's it's you know, it's one of the most rewarding things that you can get as a as a software engineer is to to get this kind of feedback from the user. 00;05;58;14 - 00;06;34;08 So, I know now that I didn't waste seven years coding this thing for nobody to use. It's I don't know that there's a lot of people happy with it and lots of users and, and people like Booking.com or Canonical using it. It's, it's, it's really motivating. It's, it's really rewarding. So, I'm quite, quite happy about it. And and not only that they, they are users there but they use it extensively and they have huge deployments and the kind of feedback you get from those those users, it's it's it's great. 00;06;35;03 - 00;07;02;09 It validates many of our decisions and invalidates others and provides feedback to make things better for the future. So, it's it's really it's really great, really happy. So as a developer myself, I can appreciate the the feeling of hearing that other people like what you've created. So, congratulations on that. Yeah, thanks. Now, you and Fred have have both talked about the admin API. 00;07;02;24 - 00;07;44;10 Can you give our listeners some details about the API and what can be done with it? And is there any functionality in the API that maybe hasn't been implemented yet? Okay. So again, a bit of historical context. So, MySQL has had support for replication for a very, very long time. Right? There was the asynchronous classic replication and before we put before Shell and the other API DBA and, and sysadmins and so on, they, they had to deploy those replication topologies manually. 00;07;44;20 - 00;08;18;09 And that involved a lot of steps, manual steps. It involved a lot of scripting, automation, monitoring and so on. And that's led to many customized, customized solutions, lots of deviations and lots of work for this. These people maintaining those architectures. And then in 2016, 2015 of them remember exactly the group replication was being developed and it came out as a preview. 00;08;19;17 - 00;08;50;17 And with that we thought. So, we have Shell, we can write APIs in Shell, we can manage instances of MySQL, so, let's do something to help users to deploy MySQL architectures. So back then, architecture based on group replication and asynchronous replication. And let's make an API to make that super easy to deploy, super easy to maintain and ...and to monitor. 00;08;51;01 - 00;09;19;28 And this is how the Admin API was born. Initially we focused on group replication because this brought a lot of great things, such as out of a lower consistency network, partition handling and so on. So that was the first focus and we, we've, we've developed the API with that in mind because group replication wasn't and still can be tricky to deploy and maintain. 00;09;20;15 - 00;09;48;07 And with the Admin API with just two or three commands, you can have your cluster up and running. It's very easy and it's very, very straightforward and it's pleasant. We tried to focus on usability a lot to make the experience pleasant, but also it's you're also it's powerful in the sense that you also can do things and configure things to the data. 00;09;48;07 - 00;10;34;13 So, so the Admin API was born from that need. And we, we introduced the support for InnoDB Cluster, but then we also added support for sandbox management. So, you can deploy sandboxes to test the solutions before going into production. You have things to help you configure the instances to be ready for the MySQL architectures. So, with a single command you can connect to an instance and the command will tell you some instances where they are not in the sense of if if the right configurations are in place and if they are not, you have another command that will just apply them for you. 00;10;34;17 - 00;11;22;26 So crazy. You also can create accounts to manage the topologies and then you have the whole set of commands to deploy InnoDB cluster, InnoDB replica set, cluster set. And the last addition is read replicas. We have integrated the whole thing and we have also integrated provisioning. So, for example, when you add an instance to a cluster, we will take a look at the GTID sets and the replications, the status of the data sets and so on, and we will guide the users to to the right provisioning method either based on replication or clone, and Shell will automate everything for you. 00;11;22;27 - 00;11;53;29 So, users will have to do any tricks and configurations. It's all integrated and with with the together with all of this, the router management that is another piece of the solutions. And one of the things we we were also careful when implementing the Admin API was to follow best practices as we would deploy the topologies with the recommended settings as defaults. 00;11;54;07 - 00;12;21;04 Then users can change of course, but we tried to follow the best practices. So, this is what the API is about. It's an API built in shell, in shell, everything is written in C++ just so the details and then those things are exposed as APIs in JavaScript and Python. So, you can access the the language of your choice, you can script it. 00;12;21;13 - 00;12;47;14 You can also call Shell with this command, the command line API. So, you can call Shell as the shell binary and in a non-interactive way, so called the shell binary. And after that you can pass the parameters to Shell and those parameters can be calls to the Admin API. This is good to integrating in other scripts or other tool things. 00;12;49;12 - 00;13;43;07 I think you asked before what's missing from the admin. That's that's the hard question that because there are so many things that can be done I can for example in with the general feeling that I get or one of the things that people ask recently is to have the an API as a standalone Python library, for example, the canonical folks were requesting that and there's there's a lot of people that's write scripts in Python to use the Admin API and those scripts have to call shell after a shell somehow there are multiple ways of doing it and then they they use the other API and some people think that it would be better if they could 00;13;43;07 - 00;14;14;21 import in their Python scripts the API is a standalone library, so this is one thing possibly missing that we might work on and provide to the users. Somewhat related would be a different approach Approach to that would be to have Shell running as a demon and with an HTTP interface and the API will in that case be exposed via REST. 00;14;15;08 - 00;14;55;22 So, people could just to the rest API calls to run the API. So, this will make the API language agnostic. So no JavaScript or python. This could be something nice. In terms of usability. So, the Admin API most of the output is JSON. This is a standard practice in this kind of API. So for example, when you call cluster starters, you get the status of your cluster in a JSON object with all the topology and the status based for every instance. 00;14;57;15 - 00;15;36;08 Maybe some people like to have a different output. For example, table or YAML, or text based and maybe add some colors on it. This could be interesting. What else? In terms of architectures? MySQL architectures there are some things missing. For example, support for multi-tier replication in replica set or or even with replicas. So, you could build trace of replication to offload servers to be something interesting. 00;15;36;08 - 00;16;16;24 There is something missing that I would like to work on eventually. That is a better framework for options management. So, option management, I mean settings of the cluster members, something better to apply a setting or no members or are a kind of this I would like to call it an options framework. So, make it easy to change options so users could do those things using the Admin API instead of logging to each instance and do the changes manually. 00;16;16;24 - 00;16;48;15 There are some things to work to integrate better. MySQL router in the sense of manage management of other instances and also monitoring. It would be nice to have something like this called self-healing. For example, you have a cluster and one of the members is missing, but it's reachable. The way to to solve that is to call a rejoin instance. 00;16;49;05 - 00;17;09;11 We have a cluster self-healing command that will call the command, and the command will take a look at the cluster status. And for example, if this is an instance missing but is reachable, will rejoin it or if it needs that the risk and needs to be called will call it. So, kind of a command to encapsulate that would be could be nice. 00;17;11;02 - 00;17;41;19 We also have some things missing regarding the enterprise features. So, support for firewall or enterprise Firewall and enterprise audit as well. Yeah. From the here that's a can remember now and also what I can share but is missing from the Admin API. So there's there's work to be done. It never gets boring. Yeah it seems so so you have plenty of new challenges. 00;17;41;19 - 00;18;09;25 So even if we reach something very mature right now, we can see that there is still plenty stuff to do. But, you know, I will tell you a secret. I have deployed maybe once or twice a group replication manually wrote all of the rest of the time. I always use the the admin API with MySQL shell and the and even asynchronous application. 00;18;09;25 - 00;18;38;23 Now I would say I don't even remember how to do it manually. Replica set is so easy to do, so there is no secret than that. So yeah, you said that MySQL Shell support so as well, which is great of course Python and JavaScript. But I've also heard from the users, you know, and I know we provide all the binaries, but there are still a lot of people in the community that likes to compile themself. 00;18;39;05 - 00;19;06;18 Their binaries, right? And they compile also the shell and the, but these guys, they tend to skip building MySQL Shell with the V8 engine, so the, the engine for JavaScript. So, I would like to ask you if there is an issue to not have a JavaScript support in the shell, because when we check our documentation or blogs most of the time everything it's written using JavaScript, right? 00;19;06;26 - 00;19;46;18 So, would it be a problem to not have a JavaScript compiling in my shell? Well, no, not at all. It's just a c-make a flag, you can disable it and you can get shell without V8 and without JavaScript support and there's no issue at all anyone can do it. And I so there are historical reasons why about your the second part of your question, the way we we have documentation and examples all written JavaScript and it's historical reasons, JavaScript was was the default of shell. 00;19;46;18 - 00;20;11;26 It's changing in the next release to SQL by the way. So, JavaScript was the default for historical reasons because of the dev API, and that's why the other API examples and so on were all written in JavaScript just because it was the default. I think now we understand that very few people use it in JavaScript and most of our users use it in Python. 00;20;12;13 - 00;20;48;01 So, I think that we should definitely start blogging and exemplifying and possibly changing the documentation to, to use to write the examples using the python. So yeah, we should definitely do that. Yeah. Thank you. Yeah. So there is no limitations to everything that you expose in JavaScript. You expose it also in Python. Right? Exactly. So like I was saying before, Shell is written in C++ and then we have language bindings and we expose the APIs in both Python and JavaScript. 00;20;48;08 - 00;21;09;15 If Shell is built without JavaScript support, then those are only exposed in Python. So there's absolutely no no limitations. And I have a favorite feature of MYSQL shell, which I'll share after you tell us what is the feature that you like the most or use most often that you don't think other people know about or don't think they use enough? 00;21;09;18 - 00;21;28;12 Has to be one. I think I have many. There's one that I think a lot of people are not at least not aware of it, and that's the built in help system. I see people relying on the API documentation and so on went online when they could have it in shell itself and it's so easy to access it. 00;21;28;12 - 00;21;57;12 Just do slash help or slash backslash help or backslash question mark. And then after it you put text and you can have access to, to the to the built in help system. So, for example, the backslash Admin API and it get the description of what the admin is, what objects are available on the API or what the classes and for example is the backslash cluster and it will print to the available cluster commands. 00;21;57;26 - 00;22;24;15 Then it can access every single command, help information. It's really, really helpful and you do it all in shell. You don't need to go to a browser or anywhere else to consult that information. And there's there's more to that. You can even, for example, connect to an instance. You establish a session to an instance, and you can access the information about the the commands you can do. 00;22;25;05 - 00;22;52;16 The backslash help, for example, show and it'll give you the information about show or transactions or all the the the supported and MySQL commands. And this is really good sometimes I'm writing a query and I need to understand or to get some extra information about some specific command. And I just do it in Shell and this is just awesome. 00;22;52;16 - 00;23;14;28 But there's, there's more. Okay. And this one Fred loves that is the plugin supports that. Fred even has a repository in GitHub with lots of plugins. So, what I also contributed to some of those and I think this there's still some people that are not aware of it. You can extend Shell, you can write your own plugins in Python. 00;23;15;13 - 00;23;46;04 It's it has become really, really easy to do it and it's awesome. I wrote my own plugins to do management of my testing environments. For example, and I love it and I think people should be, should be, should use it more. So that's one of my favorite features. I have more. I don't know if you want to share your Scott Well you stole mine...it was the help system. 00;23;46;06 - 00;24;13;09 Oh right. Oh cool. Yeah I use that. I use that all the time because I just can't remember the, the exact syntax or most of the time it's, it's trying to make sure that I have the options right for whatever, you know, configuration block...
/episode/index/show/d0cd255f-ccaf-4b55-a7da-5825f8230161/id/31152458
info_outline
MySQL Goes LTS! (Stories From the Cloud)
04/22/2024
MySQL Goes LTS! (Stories From the Cloud)
The MySQL Team has implemented a new versioning model that includes LTS. Geir Hoydalsvik, Senior Director of Software Development for MySQL stops by to give a primer on this new versioning model and breaks down the differences between the '8.0' releases and the 'Innovation' releases. ------------------------------------------------------- Episode Transcript: 00;00;09;13 - 00;00;31;20 Welcome to Inside MySQL: Sakila Speaks, a podcast dedicated to all things MySQL. We bring you the latest news from the MySQL team, MySQL product updates and insightful interviews with members of the MySQL community. Sit back and enjoy as your hosts bring you the latest updates on your favorite open-source database. Let's get started. 00;00;32;01 - 00;00;55;00 Hello and welcome to Sakila Speaks, the podcast dedicated to MySQL. Hi, I'm leFred and I'm Scott Stroz and I'm Geir Hoydalsvik. Yeah. Today our guest is Geir Hoydalsvik, software developer, director, responsible for MySQL development and maintenance of the MySQL database. This includes the following teams: server General, Runtime Optimizer, InnoDB, Server QA, and Sustaining. 00;00;55;04 - 00;01;19;15 Am I right? Yeah, that's correct. Geir, in April, the very first LTC version of MySQL will be released. Can you tell our listeners why this is significant? Yeah, that's the answer to kind of a customer and user request is to have stable releases that people can pick up security bug fixes, for example, without risk of having regressions by new feature and so on. 00;01;19;15 - 00;01;47;18 So, the long-term support release that we call LTS is actually stable for eight years, that people can buy support for this time period and essentially, they're guaranteed stability for a long time. Thank you. So between the LTS, so the major release, we will also release innovation releases. So, are those developments releases, or are there also production GA quality? 00;01;47;28 - 00;02;42;26 Thank you. A good question. They are also production quality. So, the current plans are that every second year we will release an LTS release and between two LTS test releases we will release, as you said, innovation releases every third month. So, there will be roughly eight of those between two LTS and they are production quality so people can get support or will get support with having these releases in production and this will be for people that are okay with more frequent changes and, and are willing to spend the energy of upgrading and so on between these and perhaps also take into account that releases features can go away deprecate old deprecated features can be 00;02;42;26 - 00;03;08;28 removed in innovation releases while they're never removed in LTS releases. So that's what people need to keep in check out, but they're absolutely useful and they will be supported. So as a follow up to that, what's the difference in the numbering between the LTS releases and the innovation releases? When it comes to version numbers, there is kind of a transition now between eight oh and eight four. 00;03;08;28 - 00;03;46;16 So, the first LTS release will be called 8.4 and that becomes in April. Then the main the LTS releases will be called 8.4.1, 8.4.2, 8.4.3, 8.4.4, 8.4.5 and up. So, the maintenance releases of all that LTS will be called like that. Then at the same time we will start producing innovation releases for a 9 series. So, there will be and I know 9.0, 9.1, 9.2 and so on up to 9.7 that is planned to be the next LTS release. 00;03;46;16 - 00;04;13;24 And I think in the future it will be probably more like 10 will be the next series and then 11, or at least that's how we think about it today. So, you can say that 8.4 is a little bit an exception there. That transition into a 9.0, 10.0, 11.0 and type of numbering. And then the second number will be the innovation release number essentially. 00;04;13;24 - 00;04;46;00 So, the main is the first one, the LTS number, and the second is the innovation, roughly speaking. So, it's our understanding that all of the MySQL products will follow the same release model, but not the connectors. Can you talk about that? That's that's correct. So, all the server-side products will follow the same LTS model. While on the connectors side, you are recommended to use the latest connectors that will then support all previous releases. 00;04;46;00 - 00;05;22;28 So. So when you use the latest, you can use the current release and everything older kind of thing. So that's how it works. And yeah, it's a pragmatic choice that we feel is what users want us to do is actually. So, when we see what will and what will happen with the LTS, something that I noticed is and for me maybe the most significant change is compared to what we had with the MySQL 8.0 is that in the LTS lifecycle, the downgrades and clone between different minor version will be supported, isn't it? 00;05;22;29 - 00;05;50;19 Yes, that is correct. So, this is a change from 8.0 train in 8.4 we will support upgrade and downgrade between any maintenance release like let's say 8.4.2 and 8.4.5 and you can go up and down between those both upgrade and downgrade and you can also clone in any direction between those two. 00;05;51;12 - 00;06;16;23 So that's also something that people have requested because they feel then they can more safely upgrade because there is an easy way to downgrade and so on if something is not working as they expected or something. So yes, thank you. This was really something that people were requesting. So that's great. Yeah, I can see how that's really going to help. 00;06;16;25 - 00;06;46;05 You mentioned MySQL 9.0. If a customer starts using MySQL 9.0 when it's eventually released, how long would that be officially supported? Using our new licensing model. The current plan is to have an innovation release every third month and then you can say that that is supported until the next innovation release. So, let's say if you're on 9.1, let's say that you're using innovation release the release called 9.1 and then three months later there will be a 9.2. 00;06;47;02 - 00;07;18;04 So if there is, for example, an issue that we have fixed in 9.1, it will be shaped as 9.2. So, people then need to upgrade to 9.2 to get that fix. That's essentially the model of innovation releases. So you need to go to the next innovation release to get the fix. And while for LTS, you will get every third month fixes to the stable LTS and that's how they differ, so to speak. 00;07;19;03 - 00;07;52;05 Another thing in in innovation releases, we will from time to time remove something that is has been deprecated before and this will not happen in in LTS releases. So, they are also stable in this respect. There is no removal or not anything that just critical bug fixes period. While innovation releases there is a little bit more the new features, removals and these things that then you need to follow the release notes on. 00;07;52;05 - 00;08;15;11 Yeah, thank you very much. So, I hope this will help people to understand our new model and the we are very expecting and looking forward the first LTS version of our MySQL. So, the first one will be it for next month. So, we are very happy with that. We are also looking forward to this, looking forward to see people's reaction on this. 00;08;15;19 - 00;08;34;13 Geir, thank you for joining us. We really appreciate it. Thank you very much. Thanks to both of you for having me. That's all for this episode. Thank you to our guest Geir Hoydalsvik and thank you for listening. Please join Scott and I again next time for another Inside MySQL: Sakila Speaks. That’s a wrap on this episode of Inside MySQL: 00;08;34;13 - 00;08;56;07 Sakila Speaks. Thanks for hanging out with us. If you enjoyed listening, please click subscribe to get all the latest episodes. We would also love your reviews and ratings on your podcast app. Be sure to join us for the next episode of Inside MySQL: Sakila Speaks.
/episode/index/show/d0cd255f-ccaf-4b55-a7da-5825f8230161/id/30938408
info_outline
The State of the Dolphin
04/09/2024
The State of the Dolphin
Wim Coekaerts, Executive Vice President of Software Development at Oracle joins Fred and Scott for the inaugural episode of Inside MySQL: Sakila Speaks. Wim gives us an update on the "State of the Dolphin" and discussed where MySQL fits into the landscape. -------------------------------------------------------- Episode Transcript: 00;00;09;13 - 00;00;31;20 Welcome to Inside MySQL: Sakila Speaks, a podcast dedicated to all things MySQL. We bring you the latest news from the MySQL team, MySQL product updates and insightful interviews with members of the MySQL community. Sit back and enjoy as your hosts bring you the latest updates on your favorite open-source database. Let's get started. 00;00;31;25 - 00;00;54;01 Hello and welcome to Sakila Speaks, our new podcast, dedicated to MySQL I'm Scott Stroz and I am leFred. Who better than Wim Coekaerts to be the very first guest on our new podcast. Wim is the Executive Vice President of Software Development at Oracle, is a well-known developer in the open-source community and a leader in several projects such as Oracle, Linux and Virtualization. 00;00;54;12 - 00;01;16;08 Oracle Enterprise Manager, MySQL and Heat Wave and various cloud services. Wim has a degree in Computer Science and from the University Catholique the Leuven in Belgium and has been working at Oracle since 1995. Wim, thank you for joining us today. We're really excited to hear about your work and your insights on the Dolphin database. Thanks Scott and thank you, Fred. 00;01;16;15 - 00;01;39;03 It's great to be here, happy to open the first podcast. So, Wim, what excites you most about MYSQL right now? Oh, there's some stuff going on, right? So I think the number one thing is the fact that we're doing a very important and great cloud service. And I know that we talk a lot about on premises databases and so forth, and obviously that's very important. 00;01;39;03 - 00;02;01;00 And the reason I mentioned the cloud side is because there's a lot of opportunities that we now have as a development team that allows us to make MySQL much better than it ever was. And the primary driver for that, and when I bring this up is because in cloud we are the DBA, we are the ones that actually have to deploy the server. 00;02;01;00 - 00;02;38;13 We have to go and do the backups and understand how that works and set replication and so forth. And it gives us a much better insight into the use of the product than we ever had before. Right? And I think that's the one thing around cloud that ask me the most is that from a development team point of view, working on a product like MySQL server in that we get a lot more input directly instead of working from customer to potentially running into a bug or getting feedback, but there is always a certain amount between the customer and our development teams. 00;02;39;00 - 00;03;04;27 And, so, with cloud we become that customer directly and it gives us a lot more direct experience and a feedback loop that's internal. And, so, a few examples of that would be a first of all, scale, right? We run thousands and thousands of servers now in production, right, for our customers, but we are the ones running it. And, so, we have to deal with performance issues. 00;03;04;27 - 00;03;34;24 We have to deal with potentially, you know, bugs that appear, how to debug that and making sure we get these bugs and security vulnerabilities and everything fixed really quickly for that that they're out there. We have a huge test farm, you know larger than ever before again because of the scale of cloud. And we learn a lot about how we can do things more easily because of automation and how to change the product to support that automation. 00;03;34;24 - 00;04;01;29 Right? And all of that stuff actually goes back into the product that is known as MySQL Server that, you know, goes both into the Community Edition and Enterprise Edition that that customers and developers can download and install locally. And so, you know, both inside of Oracle and inside the development team and from customers, there's this feedback that says, well, you know, you all need to talk about the cloud development and what's in it for us. 00;04;02;16 - 00;04;29;06 And I think that what I just mentioned really is what's in it for everyone else. The bugs we find, the performance issues, we find they all go back into the product. The enhancements we make to simplify things and, you know, feedback from our own use almost back into the server. Of course, when it's applicable to the server and not something more around a control plane in the cloud itself and the orchestration. 00;04;29;18 - 00;04;59;04 But there's a lot of that stuff that goes back into the product set itself. And that's you know when I say most excited that's probably the, the number one. Then I would say secondly, you know, we are also doing things that are very innovative. And again, some of this is cloud only, such as working on the heat wave engine and working with machine learning and artificial intelligence integration. 00;04;59;05 - 00;05;21;07 So certainly, Gen AI work in vector database support and improving the optimizer for some of this work. And I wanted to point that out again as well. So, as we did Heat Wave, which is specifically tied to the cloud service side, we have to make a great number of changes on the optimizer in MySQL to support that. 00;05;21;20 - 00;05;45;23 And by doing these really, really high end incredibly fast areas. And you know of course running benchmarks like TPCH and TPCS and so forth, we learn of a lot of potential deficiencies in the older optimizer. And so now we're working on hyper graph a lot more and where we're enhancing that and that will benefit again everyone else as well. 00;05;45;23 - 00;06;12;22 They use heatwave or not, whether they use the cloud or not. And so anyway, so I think, you know, our development teams are really working on cutting edge stuff. We just released JavaScript support in MySQL in ...on OTN - Oracle Technology Network - for download that everyone can use for testing development freely downloaded, and that brings JavaScript support into MySQL Server itself. 00;06;13;07 - 00;06;43;29 And then of course we have my router which added support for REST API calls a while back. And so, if you think about it, you can now write an application, let's say from your cell phone you have a basically a cell phone app or a mobile phone app that just does REST API calls to MySQL Router and from MySQL Router direct API calls go into the database and your business logic runs in the database itself and gets the data from the database. 00;06;44;10 - 00;07;12;10 So, you don't need a real middle tier anymore. And you can simplify data access and the actual business logic all combined into the server. So, it's pretty unique compared to all the other databases that ask directly competes with the implementation of JavaScript using Graal VM and as some of you might know with Graal VM we might also or will also start supporting other languages in the future. 00;07;12;10 - 00;07;42;23 So think about Python in the database and of course Java in the database. Those are all roadmap items. Can’t give you specific dates on that because you know, we're just beta, which we had one, but in the end we are moving forward with a good ecosystem of multilingual support in the database directly that supports, you know, a better security model, faster access to data, because the data and the business logic run within the same environment and everything from at with the router. 00;07;42;23 - 00;08;08;00 And then of course, you know, I'd say one last thing here. The VS Code plug in that the team has worked on and since VS Code is one of the most popular IDEs out there today, that of course, you know, it has so much functionality built in now with perf hub support as well as you can see performance data right included in the in the editor and of course direct connectivity with your database. 00;08;08;00 - 00;08;35;04 So there's a really nice ecosystem around developers with VS Code, with the router, with rest APIs you can use or the Oracle REST Database Service as well if you want that supports MySQL as well. And then of course, all the all the stuff that we're doing around cloud and security that ultimately flows into my MySQL server. So it's a very long answer to a short question, but obviously there's tons going on. 00;08;35;09 - 00;08;55;22 Well, when there's a lot of stuff to be excited, it's good to have a long answer. Why do you think MySQL is so popular with the top open-source projects? It always has been, I suppose. Right. And, you know, I think it's just a continuation of the of the past. So,MySQL was really fast and still it's really fast. 00;08;55;22 - 00;09;37;25 It was really simple to get it right next to the list really simple to install and getting up and running. It's so it's really easy to install and it's ubiquitous. It runs on every operating system in every CPU architecture you can think of. And so, if you want to build an app and have flexibility and have a very small footprint, let's say a raspberry Pi, which with for applications running MySQL server, it works just fine and all those areas and because a lot of the drivers are in standard and the standard package is a lot of the libraries support MySQL out of the box open-source tools and open-source libraries and 00;09;37;25 - 00;10;05;09 SDKs and projects there is very little additional development to do to get going with MySQL and so you know that's that was an I think still into the main driver and will continue to be. And I also think that we have, you know a lot of work on MySQL server over the years and obviously are still heavily, heavily invested in it and continue to do so. 00;10;05;24 - 00;10;45;26 And it shows the community and the users that, you know, we are our in all of this and, and it's important. So, it's a great it's a great platform. Yeah. Thank you. So, because you were talking about the MySQL community. So where do you see the future opportunities and direction for the MySQL community then you discussed about the like and now even the application or the system inside the database, which was something, for example, that we were not doing much in MySQL due to get to slow procedural kernel not that good. 00;10;46;05 - 00;11;08;03 So now with all this stuff, do you see this is the direction that we need to go? I think so, and I certainly hope so, because that's, you know, that's what we are working on. The you know, there is a lot of complexity in sort of the existing world today. Right. You have to install the middle tiers, you have to fill the databases, you have to get the clients going. 00;11;08;04 - 00;11;36;24 I think that cloud application development forced people to start using REST APIs a lot and automatically disconnect. So again, for us to put more effort into support for APIs as a front end to a database makes it a lot easier for new developers to get started That might not have database experience. So, it opens up MySQL to a broader development team. 00;11;37;07 - 00;12;04;08 Unknown But also, you know, the scripting language in in MySQL and other databases. Lots of developers don't really learn that anymore. They want to use something that that they use for their everyday job. And so ,if lots of people are using Java and JavaScript and Python on the in their in their job for developing applications every day and then have to switch to a different language in MySQL or in another database. 00;12;04;19 - 00;12;27;10 that's an actual learning step. And if you don't do it all the time, there's always the startup time that basically is a waste of time or an extra amount of effort that that people don't really like to do. And so by making it really easy to access the data, then it makes it a lot easier to build and much faster to build applications. 00;12;27;10 - 00;12;55;03 And then secondly, we obviously are very focused on ensuring that MySQL Server, whether you run it on prem and whether you run it in cloud with our MDS service, MySQL database service, that that remains the same. And so that when you develop locally with an deploy and cloud which happens more and more for everyone, that's sort of the nature of how the IT business is evolving. 00;12;55;11 - 00;13;26;26 It makes it a lot easier to make that migration stuff and adding HeatWave on top of that again, we could have made HeatWave an independent service with its own access layer, but since MySQL is so popular and well known and easy to use, having the HeatWave engine built into MySQL and make it basically transparent allows us to expand that whole environment without the user or the developer having to make any application changes. 00;13;27;10 - 00;13;50;17 It will help you want to do data warehousing, no problem. You want to ingest data from object storage through Lakehouse. No problem. You want to do machine learning on your data. It's all in the same database. And so, I think one direction being cloud and I think that the MySQL community in general, yes, that's good for for the community as well. 00;13;50;17 - 00;14;24;25 It's not just about the on-premises installation of the server, but in general things we can do in this... in this case. And so that will be the I think the main opportunity and direction for the server. And then you know, Gen AI and to... Gen AI has sort of two angles to add. One is how can we provide MySQL with better support for developers that want to do their own interfaces and applications on top of Gen AI. 00;14;24;26 - 00;14;57;26 And then the other aspect of it is how can we create sort of a natural language interface to the server so that you can basically say, please get me all the data from that, every department where, you know, employees have been out for 3 days and I'm just making something up on the player. But basically you can, you can have a natural language sentence which we then transform into a SQL statement in the back end towards MySQL. 00;14;57;26 - 00;15;26;09 Well, it's just an example, but you see a lot of that type of stuff being worked on at Oracle, but also, of course, our competitors. And it totally changes how we interact with products and also change how interfaces are designed in the future. I think that is something we want to make sure MySQL is part of as well and stay current with this stuff. 00;15;26;09 - 00;15;50;17 Awesome. As we mentioned before, you're a pretty prominent figure in the Linux ecosystem. If you were to compare the MySQL ecosystem to the Linux ecosystem and what would you say are the biggest differences between the two? Well obviously, you know, when we talk about Linux, you know, are we talking about Linux, the kernel development or are we talking about Linux distribution environment, that all operating system environment? 00;15;50;17 - 00;16;11;14 Right. So, there's so I think, you know, for one, there are two Linux ecosystems and so let's say we'll take the Linux kernel as the of the ecosystem to compare that because it's, you know, one development for, for something pretty big, the you know, to me the main difference between the two is that with MySQL they do all the development. 00;16;11;24 - 00;16;40;16 So, it's basically MySQL development driven from one company slash organization with some contributions. I don't want to... obviously people report bugs. Can people test our software and find problems that need to be fixed or in some cases some companies will provide some code to us. But by and large the bulk of the work is done by us. 00;16;40;24 - 00;17;19;19 By the Oracle MySQL Development Team. We're of course with Linux kernel development that is done by everyone. There is no specific owner, there is no particular organization that's providing the bulk of the code. It's quite well spread across and you know, there's advantages and disadvantages of both. But, but I think that that is the main difference is that from when we speak, when we talk about MySQL community, in MySQL developer community, we're really talking for the most part about developers using MySQL as the underlying database. 00;17;20;10 - 00;17;46;27 Whereas when you talk about Linux, then you either have the Linux developer community around the Linux kernel or various Linux ecosystem, you know, distribution, libraries and such or Linux developers, which are really application developers that use Linux as the underlying buffer. Right? And so it's really the latter where, where you could have that comparison in other ways. 00;17;46;27 - 00;18;17;25 They are, you know, that's the big difference with the bulk who does the bulk of the development and the contribution. Now, I think that that the connection with MySQL from a user slash developer is much tighter than with Linux because the Linux side, you pick a distribution, there's many of them, but there's also tons of developers and windows and tons of developers on Mac OS and you know, other other platforms that that are still used out there. 00;18;17;25 - 00;18;42;09 And MySQL is on all of those platforms, right? And so, I think that the main differences are one, the developer community and the role that they play. And then two the again, ubiquitous does deploy many of MySQL across operating systems. So, a developer doesn't necessarily need a tie to a particular OS to do MySQL development. 00;18;42;09 - 00;19;21;07 And so, I think that those are the the two big differences that I can think of. And, you know, quite frankly, when you when you do when you study computer science or so in general, operating system development is something that is more often than database development. And I'm talking when I'm talking about learning SQL or something like that, I'm talking about building a database itself, building the code for doing an optimizer and so forth that is not as widespread in, in universities or colleges or so. 00;19;21;07 - 00;20;01;06 And so, it's easier, I think, to start with an operating system, certainly with Linux and do some development and fix some bugs and and so on. There's there's more generic knowledge around that, which probably makes it a little bit easier to open up. But one of the advantages, again, that MySQL has over other databases out there, certainly other open-source databases in and in colleges and higher education is that it is your one platform that tends to be used for teaching database development because it is still relatively small in size and it is well compartmentalized and easier to do code reviews of it. 00;20;01;06 - 00;20;32;05 So, there's that. Yeah, thank you very much. So, you said earlier that because we entered into AI area, right? And to you give us a review an answer to that telling that we there is a plenty of people working on that and it would be very nice that we could talk to a database like just by a human words. 00;20;32;05 - 00;20;58;23 And it will do the all the stuff for us to to get the data. So, this is what do you think it would be to the future of using the database and MySQL in particular. So yeah, you know, I guess there basically are two aspects that we are working on, right? One is how do you interface with the database? 00;20;59;00 - 00;21;28;06 And so when you talk about Gen AI and it typically would be, you know, in national natural language to SQL pace, which would be powered by an AI can do text voice to text and then go from text to SQL basically right. And that's a multi-step approach and it's not easy to build those problems and take care of the aspects. 00;21;28;06 - 00;21;57;19 It's the multi-stage way from...
/episode/index/show/d0cd255f-ccaf-4b55-a7da-5825f8230161/id/30746513