Complex normalized schemas can make database systems slow and inefficient. This presentation explores a storage layer that eliminates most joins in such systems by pre-joining the data. Data in this storage layer can be accessed using an object API without the overhead of an object-relational mapping layer. It can also be accessed using standard SQL for efficient complex multi-table reporting.
Aside from traditional master-slave setup used mostly for HA and read scale-out, there is an established history of attempts at multi-master replication with MySQL. In this presentation we will look at what multi-master replication can do for us and compare different approaches of doing it.
Google engineers talk about the long fight against the specter of data drift. Starting from historical FUD about data drift, Google SREs will discuss design and implementation of a solution to detect data drift on any slave without downtime, and lessons learned from deployment and running in a world with detection.
Drizzle has thrown out the MySQL replication system and has started from scratch in implementing its own replication architecture. In this session, we'll take a look at the basics of the new architecture, what tools are available, and discuss possible future functionality. An example setup will also be presented.
MySQL replication has been a critical part of scaling Facebook's storage infrastructure. However, it brings with it the fear of divergent replicas. This session discusses a new tool that detects divergences, identifies inconsistent data, and helps repairs defects.
Want to really scale PostgreSQL using the new binary replication? Learn how to set up hot standby, streaming replication, failover, non-persistant databases and cloning to scale PostgreSQL 9 for reads.
MySQL replication deprivation is a common condition that occurs when you encounter problems built-in MySQL replication cannot solve. Do you need automatic master promotion, ability to replicate to PostgreSQL or Oracle, multi-master/multi-source replication, parallel slave apply, or built-in consistency checking?
MySQL's replication system has been a core feature often touted for scaling (sort of) and redundancy (sort of). I'll describe a client's extensive use of MySQL replication (they have more than 200 MySQL instances replicating to one another) as a reference for the many uses and misuses of replication.
The developers behind MySQL Replication describe the new features. After a quick review of what MySQL 5.5 brings, focus turns to the features that are coming after MySQL 5.5.
This is updated and revised version of tutorial done at MySQL Conference
Getting sharding right is crucial for achieving high scale with MySQL on commodity hardware like we do at Facebook. We will overview sharding best practices, and show some examples of both successful and unsuccessful methods at sharding MySQL.