MySQL High Availability at GitHub

GitHub uses MySQL as its main datastore for all things non-git, and its availability is critical to GitHub’s operation. The site itself, GitHub’s API, authentication and more, all require database access. We run multiple MySQL clusters serving our different services and tasks. Our clusters use classic master-replicas setup, where a single node in a cluster (the master) is able to accept writes. The rest of the cluster nodes (the replicas) asynchronously replay changes from the master and serve our read traffic.

The availability of master nodes is particularly critical. With no master, a cluster cannot accept writes: any writes that need to be persisted cannot be persisted. Any incoming changes such as commits, issues, user creation, reviews, new repositories, etc., would fail.

To support writes we clearly need to have an available writer node, a master of a cluster. But just as important, we need to be able to identify, or discover,

Original URL:

Original article

Is Serverless Just a New Word for Cloud Based?

Rick Golba

 | June 20, 2018 | 

Posted In: Amazon RDS, AWS, Cloud and MySQL, Cloud and NoSQL, MariaDB, MongoDB, MySQL, PostgreSQL
Serverless is a new buzzword in the database industry. Even though it gets tossed around often, there is some confusion about what it really means and how it really works. Serverless architectures rely on third-party Backend as a Service (BaaS) services. They can also include custom code that is run in managed, ephemeral containers on a Functions as a Service (FaaS) platform. In comparison to traditional Platform as a Service (PaaS) server architecture, where you pay a predetermined sum for your instances, serverless applications benefit from reduced costs of operations and lower complexity. They are also considered to be more agile, allowing for reduced engineering efforts.
In reality, there are still servers in a serverless architecture: they are just being used, managed, and maintained outside of the application. But isn’t that a

Original URL:

Original article

Show HN: Mergeable – GitHub bot to ensure consistency in PR and Issues


A bot that enforces consistency and standards on your GitHub projects and repositories.

Key Features •
Vision •
Configuration •
Usage •

Key Features
Pull Requests
Validate pull requests for mergeability based on content and structure of your PR (title, labels, milestone, project, description, approvals, etc). The rule-sets are fully configurable. Here are a few examples of what you can do:

Prevent accidental merging of Pull Requests that are work in progress by labeling it wip or prefixing the title with the abbreviation.

Ensure all Pull Requests have a description so that when you view through history you still have context.

Ensure that all Pull Requests are approved by a specific list of users. It is especially useful if one of the users is not a collaborator of your repository — something GitHub does not already support.

Ensure that all Pull Requests merged are in a specific GitHub Project.

Original URL:

Original article

Proudly powered by WordPress | Theme: Baskerville 2 by Anders Noren.

Up ↑

%d bloggers like this: