Monday, May 20, 2013

More details on "MySQL 5.6 Experiences" coming soon...

I've already shared my presentation few hours before I made it during PLMCE 2013, back on April 24. The idea behind the presentation was simple (and I think that any MySQL user who is planning to upgrade to MySQL 5.6.x in production should do something like this): let's read the "What Is New in MySQL 5.6" manual page and check new features one by one.

This is what I am going to do with the content of that manual page in the upcoming blog posts (and what was done as background work for the presentation):
  • Remove extra details and add references to each major feature
  • For every feature description add extra references (articles about the feature, bugs related to the feature).
  • Add some comments based on personal experience (if any)
References in the presentation are "tagged" with "#" (if they are about bugs), "?" (if they are about problems either solved with this new feature or appearing because of the way this new feature is implemented or operates with other features or typical user assumptions) or with "!" (if they are about solutions, HOWTOs or explanations on how to use new features in the best way, or describe positive experience with this new feature). This way you can easily pick up what to read, depending on your needs and preferences. Some people, like me, prefer to be informed about problems, while others care mostly about positive experience.

During the upcoming weeks I plan to explain every slide in more details (as 50 minutes were not enough for this) here, grouping them by topics (security improvements, InnoDB improvements etc) and check status of all the active bugs mentioned in it (it makes even more sense now, when 5.6.12 is released). I'll also check and comment on new bugs for each major feature mentioned (if any).

The goal of this upcoming series of posts ("MySQL 5.6 Experiences") is to give enough information and references for any interested MySQL user to be able to decide if any of new features are important and mature enough to be used in production and, thus, does it really make sense to upgrade to MySQL 5.6 right now. I do not want to just share optimistic "the best release ever" or pessimistic "buggy and not mature to be used in production" statements - I want to provide some background.

No comments:

Post a Comment

Post a Comment