One of the main advantages of MongoDB is the high-availability, redundancy and strict consistency, which is implemented with Replicasets - group of Mongo database which runs simultaneously and contains the same data. The idea is that once one of the sets fails, another one will take his job to response, even it was the primary set. It's totally automatically failure-safe and one of the basis of production deployment. In this article we will explain how to deploy such an environment including architecture.
The BillRun is built on MongoDB, which is the open-source, document database, popular among developers and IT professionals due to its agile and scalable approach. MongoDB is also known as the leading NoSQL database technology.
Recently, we've received a lot of questions about how we implemented a billing system without a database which supports transactions nor row locks.
In this article we will try to explain how to verify integrity and concurrency using a MongoDB database. In addition, this article dispels the myth about MongoDB not being able to deal with ACID (atomic, consistent, isolated and durable) operations.
After the previous MySQL Master-Master Replication, we recommended to add slaves to Masters, to reduce load on the masters.
In this article we will describe how add slave to one of our masters. You can continue to add slave(s) to another master as the this process.
We will continue the previous post, and assume we have two masters - Server A and Server B, and we will add Server C as slave for Server A.
We are using AMI (Amazon EC2) distribution, but you can use your favor Linux distribution.
Page 14 of 15