New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Database redundancy #71

Open

michaelbontyes opened this issue Oct 18, 2023 · 0 comments

Labels

devops

Collaborator

michaelbontyes commented Oct 18, 2023

We're looking for database redundancy in case of any failure.

The scenario is:

The main OpenMRS database is continuously and automatically synced to a secondary database as master-master or master-slave architecture.
The main OpenMRS database the backend uses is failing - not responding anymore.
The OpenMRS backend automatically switches to the secondary database to keep EMR operations running.
Once fixed, the backend switched back to the primary database / normal behavior again.

Requirements and assumptions:

OpenMRS 3 is running on Docker-compose
Databases (MariaDB) instances are running on Docker-compose on the same network, but potentially on different devices/laptops.

Task:

Modify the docker-compose and create necessary configuration files to add that functionality

michaelbontyes added enhancement devops and removed enhancement labels

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment