Thursday, March 23, 2017

The history and future of the MySQL Ecosystem

This week I was the guest speaker at the New York Linux Users Group (NYLUG) Meetup where I had the opportunity to talk about The history and future of the MySQL Ecosystem. This talk, titled “”Spaghetti and MySQLBalls (with a side of greens)” detailed the beginnings of MySQL, the MySQL acquisition history, described the state of current MySQL versions/variants/forks, storage engines, related vendors and much more. It was actually great to reminisce and share some of the great stories of the fantastic team at MySQL Inc/AB, and it amazed me as I presented just how many former employees have created companies in the ecosystem.

These Linux guys were also a great group to talk to, with lots of good questions and feedback. Many thanks to comments verbally and online including, “One of the best meetups I have been to. Ronald Bradford gave a great talk.”, “Ronald’s presentation was great. … the presentation really helped clear up a lot of longstanding confusion on the myriad of MySQL choices available…” and “Superb presentation and exactly what it said on the tin.”

A video of the presentation will be available soon.

Secrets of mysqlnd Presentation

At the recent New York PHP Group in New York, I gave a presentation on “Secrets of mysqlnd”. While there are no real “secrets” of the new MySQL Native Driver for PHP, available in PHP 5.3, and the default for PHP 5.4+ replacing libmysqlclient, there are new features of the driver many are unaware of. If you have ever had to fight the gods with compiling a particular version of PHP with the right libmysqlclient dependency, the good news is that legacy requirement is no longer necessary.

Some of the topics discussed in detail included support for read/write splitting and load balancing with existing applications, and the implications for consistency with MySQL replication. Mysqlnd can also provide failover capabilities, and when combined with using MySQL cluster, Tungsten Replicator and HA manages including MMM and MHA, a more smoother application management of failover in the future may be possible with applicable design.

Mysqlnd also provides a number of other plugin extensions which shows the potential of this new driver for the future. There is still a lot of work to be done, particularly with getting distros and package management to support all capabilities for ease of installation and management.

Better MySQL Security and Administration

With the recent cyber attacks and breaches with data from large organizations including Sony, is your MySQL data safe? What are the best practices for securing and administering your MySQL environment? In this presentation we will cover the essential steps for better MySQL security. We will also cover the different installation and administration tasks necessary to ensure your data is managed.

Presenter: Ronald Bradford
Schedule: Insight Out DB Showcase. October 2011 Tokyo, Japan

Reasons to use MySQL 5.5

There are a number of significant new features in MySQL 5.5 including semi-synchronous replication, SIGNAL and RESIGNAL, the PERFORMANCE_SCHEMA, additional STATUS variables, new partitioning options, different default storage engine, better UTF8 support and removal of deprecated functions just to list key considerations.

However some of the performance improvements are worth the investment of time. For a high concurrency InnoDB environment one new configuration alone can provide a 50% improvement in performance. Other settings can help in the reduction of downward spikes in performance due to internal InnoDB disk management. Some new configuration settings are off by default. See the actual benefits of these new features and what you should be using to maximize your database performance.

Presenter: Ronald Bradford
Schedule: Effective MySQL Meetup York. June 2011 New York

MyISAM

MyISAM is the default storage engine of MySQL until version 5.5. This engine is an implementation of the well defined database storage ISAM architecture and has been available since MySQL 3.x.

Key features
• Non transactional
• Fast insert rate
• Btree based indexes
• Supports FULLTEXT index
• 16k data pages
• 4k index pages

Limitations
• Does not support transactions
• Table level locking on DML and DDL statements
• Not crash safe
• Relies on File System level cache to cache data pages

Important Parameters
[Read more...]