Giuseppe Maxia

Quality Assurance Architect, VMware

Quality Assurance Architect at VMware. Formerly at MySQL AB, and then through acquisitions at Sun Microsystems and Oracle. Then at Continuent, Inc and currently at VMware through a merge. I am active member of the MySQL community and long timer open source enthusiast. During the past decades I have worked in various IT related fields, with focus on databases, object oriented programming, system administration, quality assurance. Fluent in Italian, English, Perl, Python, SQL, Spanish, C, Bash, and good speaker of C , French, Java. I work in cyberspace, with a virtual team.


Partitioning is a feature of MySQL that has been around since version 5.1. It is a method of improving database speed beyond the limits of indexes and available memory. When used appropriately, it can increase performance by several orders of magnitude. Amid some doubts, it was overshadowed by more flamboyant features in MYSQL 5.5.
Starting with MySQL 5.6, and continuing with MariaDB 10.0 and MySQL 5.7, there has been a rush of new replication features: * Parallel replication * Global Transaction Identifiers * Multi source replication * Crash safe tables. How good are these features?
Database replication, in its simplest definition, is just data flowing from a master to some slaves. Until recently, the most daring topologies adopted by DBAs was a master-to-master deployment, with perhaps a DRBD in between. The times of circular replication are over!