Database redundancy #71
Description
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