Repository navigation
Vinicius Grippa
I started with MySQL when I was a junior DBA at a Brazilian company. That was back in 2014, and the version I worked with was 5.1, while MySQL 5.6 was being released around that time. The good old days when the MyISAM engine was king! :D
The first one was Peter Zaitsev, the founder of Percona, and the other was LeFred. They were and still are absolute legends in the community, and they continue to inspire people every single day.
First and foremost: be humble. It is insane how many smart people exist in the MySQL community. You will always find someone who has something to teach you if your ears are open to listen!
FOSDEM for me is the main event of the year. It has a great capacity to bring together members of the community from all over the world. Besides the friendship, it is an event where people share the latest innovations and the most advanced technical sessions in the MySQL ecosystem. It is also a great place to spark ideas for the next cycle of work in MySQL.
I think MySQL 8 brought many great features, such as dynamic redo log adjustment and the ability to create invisible primary keys. Invisible primary keys allow legacy applications where tables do not have PKs to keep their behavior without needing any code changes, while still improving database performance through primary keys. This is particularly useful for environments where replication is active.
Force everyone to use Primary Keys! 😛 Jokes aside, I would love to see MySQL support extensions the way Postgres does, along with better AI support. The good thing is that this is coming fast, and I expect to see both in upcoming releases.
It sounds simple, but it is still commonly misunderstood: how indexes actually work. People assume an index is supposed to fix any performance issue you might have. Because of that, I have seen countless cases where a table had more indexes than columns, even using more disk space for indexes than the data itself. In databases, there is an unwritten rule that every time you improve something, you have to give up on something else. If you create an index, you might gain read performance, but you lose write performance and disk space.
Many people nowadays consider MySQL not to be the right database for modern applications. I think if they saw how active community members are shaping and adding features to MySQL, they would be surprised by how many new things are coming out so fast. There are companies in the ecosystem like Readyset, VillageSQL, and ProxySQL that bring a lot of value to the table. Besides still being the most well known open source database according to DB-Engines, it is definitely a good time to pay attention to the ecosystem.
Debugging performance issues is definitely the most interesting problem for me! Collecting perf data, creating flame graphs, and analyzing the source code are really fun to do and can teach you a lot of things. The performance category goes way beyond just creating indexes to fix slow queries!
It may sound like following a trend, but definitely AI. It really changed our relationship with technology. The models are becoming smarter and faster, and they truly help people improve productivity and explore new ideas. Plus, this will generate an explosion of data, so I am also excited to see how we will handle all this new data being produced by AI agents.