web.archive.org/web/20160920153829/http:/githubengineering.com/context-aware-mysql-pools-via-haproxy

Preview meta tags from the web.archive.org website.

Linked Hostnames

1

Search Engine Appearance

Google

https://web.archive.org/web/20160920153829/http:/githubengineering.com/context-aware-mysql-pools-via-haproxy

Context aware MySQL pools via HAProxy

At GitHub we use MySQL as our main datastore. While repository data lies in git, metadata is stored in MySQL. This includes Issues, Pull Requests, Comments etc. We also auth against MySQL via a custom git proxy (babeld). To be able to serve under the high load GitHub operates at, we use MySQL replication to scale out read load.



Bing

Context aware MySQL pools via HAProxy

https://web.archive.org/web/20160920153829/http:/githubengineering.com/context-aware-mysql-pools-via-haproxy

At GitHub we use MySQL as our main datastore. While repository data lies in git, metadata is stored in MySQL. This includes Issues, Pull Requests, Comments etc. We also auth against MySQL via a custom git proxy (babeld). To be able to serve under the high load GitHub operates at, we use MySQL replication to scale out read load.



DuckDuckGo

https://web.archive.org/web/20160920153829/http:/githubengineering.com/context-aware-mysql-pools-via-haproxy

Context aware MySQL pools via HAProxy

At GitHub we use MySQL as our main datastore. While repository data lies in git, metadata is stored in MySQL. This includes Issues, Pull Requests, Comments etc. We also auth against MySQL via a custom git proxy (babeld). To be able to serve under the high load GitHub operates at, we use MySQL replication to scale out read load.

  • General Meta Tags

    8
    • title
      Context aware MySQL pools via HAProxy - GitHub Engineering
    • content-type
      text/html; charset=utf-8
    • viewport
      width=device-width, initial-scale=1.0, maximum-scale=1
    • octolytics-app-id
      internal-engineering-blog
    • description
      At GitHub we use MySQL as our main datastore. While repository data lies in git, metadata is stored in MySQL. This includes Issues, Pull Requests, Comments etc. We also auth against MySQL via a custom git proxy (babeld). To be able to serve under the high load GitHub operates at, we use MySQL replication to scale out read load.

  • Open Graph Meta Tags

    5
    • og:title
      Context aware MySQL pools via HAProxy
    • og:description
      At GitHub we use MySQL as our main datastore. While repository data lies in git, metadata is stored in MySQL. This includes Issues, Pull Requests, Comments etc. We also auth against MySQL via a custom git proxy (babeld). To be able to serve under the high load GitHub operates at, we use MySQL replication to scale out read load.
    • og:url
      https://web.archive.org/web/20160824004242/http://githubengineering.com/context-aware-mysql-pools-via-haproxy/
    • og:site_name
      GitHub Engineering
    • og:type
      article

  • Twitter Meta Tags

    3
    • twitter:card
      summary
    • twitter:site
      @GitHubEng
    • twitter:creator
      @ShlomiNoach

  • Link Tags

    12
    • alternate
      https://web.archive.org/web/20160824004242/http://githubengineering.com/atom.xml
    • canonical
      https://web.archive.org/web/20160824004242/http://githubengineering.com/context-aware-mysql-pools-via-haproxy/
    • profile
      http://gmpg.org/xfn/11
    • shortcut icon
      /web/20160824004242im_/http://githubengineering.com/images/favicon.ico
    • stylesheet
      https://web-static.archive.org/_static/css/banner-styles.css?v=1B2M2Y8A

Links

25