http://simonwillison.net/2018-06-20T23:05:29+00:00Simon Willison2018-06-20T23:05:29+00:002018-06-20T23:05:29+00:00https://simonwillison.net/2018/Jun/20/mysql-high-availability-github/#atom-tag

<p><strong><a href="https://githubengineering.com/mysql-high-availability-at-github/">MySQL High Availability at GitHub</a></strong></p> Cutting edge high availability case-study: GitHub are now using Consul, raft, their own custom load balancer and their own custom orchestrator replication management toolkit to achieve cross-datacenter failover for their MySQL master/replica clusters. <p>Tags: <a href="https://simonwillison.net/tags/github">github</a>, <a href="https://simonwillison.net/tags/highavailability">highavailability</a>, <a href="https://simonwillison.net/tags/mysql">mysql</a>, <a href="https://simonwillison.net/tags/scaling">scaling</a>, <a href="https://simonwillison.net/tags/shlominoach">shlominoach</a></p>

2018-06-19T16:12:42+00:002018-06-19T16:12:42+00:00https://simonwillison.net/2018/Jun/19/thoughts-on-foreign-keys/#atom-tag

<p><strong><a href="https://github.com/github/gh-ost/issues/331">github/gh-ost: Thoughts on Foreign Keys?</a></strong></p> The biggest challenge I’ve seen with foreign key constraints at scale (at least with MySQL) is how they conflict with online schema migrations using tools like pt-online-schema-change or GitHub’s gh-ost. This is a good explanation of the issue by Shlomi Noach, one of the gh-ost maintainers. <p>Tags: <a href="https://simonwillison.net/tags/databases">databases</a>, <a href="https://simonwillison.net/tags/mysql">mysql</a>, <a href="https://simonwillison.net/tags/scaling">scaling</a>, <a href="https://simonwillison.net/tags/sql">sql</a>, <a href="https://simonwillison.net/tags/shlominoach">shlominoach</a></p>