MySQL Consultant, Slice Technologies
Software architect Stéphane Combaudon worked for Percona in 2012-2016 after working as a MySQL DBA for leading French companies such as Dailymotion (a video streaming service) and France Telecom. He uses the experience he’s acquired over the past 11 years to not only solve challenges and objectives, but also contribute new and innovating solutions to every project he works on. While working for Percona, Stephane blogged a lot in Percona Data Performance Blog to share his constant search for learning new things keeps his skills sharp, knowledge. His posts routinely received hundreds of Facebook “Likes,” tweets and social shares, mainly because so many readers found them helpful to what they were working on as DBAs and developers. That desire to give back to the MySQL community is why he enjoys speaking at conferences around the world, including Fosdem, Froscon and the Percona Live MySQL conferences each year in both London and Santa Clara, California. Stéphane, who lives in Paris with his wife and their twin daughters, enjoys spending time with his family when not working. He’s also an avid chess player, participating in several tournaments annually.
Global Transaction IDs (GTIDs) in MySQL 5.6 are a great addition as they are supposed to ease replication administration a lot. But they are also changing some old habits and they require careful planning when enabling them. Learn the benefits and gotchas of GTIDs in this talk.
Many organizations use NoSQL solutions along with a relational database system, and the combination of MongoDB with MySQL is popular.
Replication has been used for a long time to provide high availability. However the traditional position-based replication has a serious drawback: a same transaction will never have the same position on two different servers. Reconfiguring replication is then difficult and error-prone, which is bad when you want to make failovers as graceful and reliable as possible. Enter MySQL 5.6 and Global... [read more]