A primary objective of MHA is automating master failover and slave promotion within short (usually 10-30 seconds) downtime, without suffering from replication consistency problems, without spending money for lots of new servers, without performance penalty, without complexity (easy-to-install), and without changing existing deployments. MHA also provides a way for scheduled online master switch: changing currently running master to a new master safely, within a few seconds (normally 0.5-2 seconds) of downtime (blocking writes only).
Group items tagged
Yoshinori Matsunobu's blog: Announcing MySQL-MHA: "MySQL Master High Availability manag... - 2 views
rtomayko/replicate - GitHub - 2 views
-
Dump and load relational objects between Ruby environments. The project started at GitHub to simplify the process of getting real production data into development and staging environments. We use it to replicate entire repository data (including associated issue, pull request, commit comment, etc. records) from production to our development environments with a single command. It's excessively useful for troubleshooting issues, support requests, and exception reports as well as for establishing real data for evaluating design concepts.
draper - 1 views
-
This gem makes it easy to apply the decorator pattern to domain models in a Rails application. This pattern gives you three wins: * Replace most helpers with an object-oriented approach * Filter data at the presentation level * Enforce an interface between your controllers and view templates.
1 - 7 of 7
Showing 20▼ items per page