Name: delmo-rails-pg-demo
Owner: Stark & Wayne
Description: This repository is for a demonstration of Delmo
Created: 2017-05-23 23:59:35.0
Updated: 2017-05-24 01:19:04.0
Pushed: 2017-05-24 01:18:37.0
Homepage: https://github.com/bodymindarts/delmo
Size: 220
Language: null
GitHub Committers
| User | Most Recent Commit | # Commits |
|---|
Other Committers
| User | Most Recent Commit | # Commits |
|---|
This repository is for a demonstration of Delmo. Delmo was originally written to help us test the failover and disaster recovery modes of Dingo PostgreSQL clusters. It has subsequently been used to test Stark & Wayne Habitat plans for clustered services such as Redis, PostgreSQL, Consul and more.
In this repo is a Ruby on Rails app that uses PostgreSQL: a distributed system of two things. The web app requires the db database. But what is the right behavior if the db is missing? An ugly 500 status page for the user to see? Or can we put in some behavior within the app to specifically handle the db temporarily being unavailable (downtime, network partition, HA failover).
First step is to write a system test that runs the web and db components of the system, turns off the db and confirms that the web app fails horribly.
The next step is to reproduce the problem in controlled environment that we can programmatically manipulate. Delmo uses docker-compose. In this production-esque environment, the Rails app shows a more cryptic error:
prod
Then we can fix the Rails app so that it does something useful whilst the database is missing - say display a static-only version of the site, without any dynamic interactive features. Whatever is useful to your users.
The third step is to write a failing test using Delmo - to programmatically deploy the application and its database, stop the database and show that the application fails, when we'd rather that it worked.
Finally, we will upgrade the application to work if the database is missing. Our Delmo test scenario will run and show that web app no longer fails when db is missing.
The system test will be run by Delmo, and the web and db components are containers within a docker-compose deployment that Delmo will manage.
This repo has four branches representing the four stages of the tutorial/demo:
git checkout step-1 - the original basic Rails app that fails when PostgreSQL is not availablegit checkout step-2 - Docker-ize the Rails app and reproduce the error within a docker-compose environmentgit checkout step-3 - Delmo test suite to show a failing testgit checkout step-4 - Rails app fixed to handle the PG::ConnectionBad error and show a static page (not the 500 error page).The read me of each step will lead on to the next step/branch.
Get started:
clone https://github.com/starkandwayne/delmo-rails-pg-demo
elmo-rails-pg-demo
checkout step-1
README.md