Episodios

  • A Rockstar Speaks

    A Rockstar Speaks
    Mar 17 2025
    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...
    Más Menos
    15 m
  • The Bug Whisperer

    The Bug Whisperer
    Feb 13 2025
    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...
    Más Menos
    9 m
  • What's in a name?

    What's in a name?
    Jan 30 2025
    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 ...
    Más Menos
    20 m
  • MySQL User Group Spotlight: MyNA

    MySQL User Group Spotlight: MyNA
    Jan 16 2025
    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, ...
    Más Menos
    22 m
  • MySQL Time Capsule

    MySQL Time Capsule
    Dec 13 2024
    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....
    Más Menos
    19 m
  • MySQL 8.4 LTS: A Balancing Innovation and Stability

    MySQL 8.4 LTS: A Balancing Innovation and Stability
    Jun 25 2024
    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...
    Más Menos
    14 m
  • Mastering MySQL Group Replication

    Mastering MySQL Group Replication
    May 28 2024
    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. ...
    Más Menos
    14 m
  • MySQL Shell Does All The Things!

    MySQL Shell Does All The Things!
    May 7 2024
    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 ...
    Más Menos
    28 m
adbl_web_global_use_to_activate_webcro768_stickypopup