https://github.com/jelastic-jps/mongodb-replication
Master-slave replication is used to solve performance problems, to support the db backups, and to alleviate system failures
https://github.com/jelastic-jps/mongodb-replication
database database-server jelastic jelastic-jps jps master-slave mongodb mongodb-database mongodb-replication nosql-database replication slave
Last synced: 29 days ago
JSON representation
Master-slave replication is used to solve performance problems, to support the db backups, and to alleviate system failures
- Host: GitHub
- URL: https://github.com/jelastic-jps/mongodb-replication
- Owner: jelastic-jps
- License: apache-2.0
- Created: 2016-05-31T11:24:48.000Z (almost 9 years ago)
- Default Branch: master
- Last Pushed: 2020-08-26T09:55:07.000Z (over 4 years ago)
- Last Synced: 2025-04-02T04:01:40.070Z (about 2 months ago)
- Topics: database, database-server, jelastic, jelastic-jps, jps, master-slave, mongodb, mongodb-database, mongodb-replication, nosql-database, replication, slave
- Language: Shell
- Homepage:
- Size: 87.9 KB
- Stars: 1
- Watchers: 2
- Forks: 8
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE.md
Awesome Lists containing this project
README
# Deprecated. Please refer to [the new repo](https://github.com/jelastic-jps/mongodb/).
[](../../../mongodb-replication)
## MongoDB Database Replication
The JPS package deploys MongoDB Cluster with preconfigured replication that initially contains 2 database containers. The package provides the solution for solving performance problems, DB backups support, gives ability to alleviate system failures. It enables data from one database server (the master) to be replicated to another (the slave).
### Highlights
This package is designed to solve a number of different problems with performance, the primary database downtime (e.g. due to hardware failure or connection interruption).
It enables data from one database server (the master) to be replicated to to another (the slave).
This primary (the master) database will process all the incoming write operations, storing the information about them within its oplog, where they can be accessed and replicated by every secondary (the slave) replica member for being applied to their data sets. In such a way, all of the servers will represent the same content and ensure its availability.
### Environment Topology
### Specifics
Layer | Server | Number of CTs
by default | Cloudlets per CT
(reserved/dynamic) | Options
----------------- | --------------| :-----------------------------------------: | :-------------------------------------------------------: | :-----:
DB | MongoDB (NoSQL) | 2 | 1 / 16 | -
* DB - Database
* CT - Container
**MongoDB Database**: 3.2.1
### Deployment
In order to get this solution instantly deployed, click the "Get It Hosted Now" button, specify your email address within the widget, choose one of the [Jelastic Public Cloud providers](https://jelastic.cloud) and press Install.
[](https://jelastic.com/install-application/?manifest=https%3A%2F%2Fgithub.com%2Fjelastic-jps%2Fmongodb-replication%2Fraw%2Fmaster%2Fmanifest.jps)
To deploy this package to Jelastic Private Cloud, import [this JPS manifest](../../raw/master/manifest.jps) within your dashboard ([detailed instruction](https://docs.jelastic.com/environment-export-import#import)).
More information about Jelastic JPS package and about installation widget for your website can be found in the [Jelastic JPS Application Package](https://github.com/jelastic-jps/jpswiki/wiki/Jelastic-JPS-Application-Package) reference.