Blog

BillRun Blog

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 theMongoDB replicaset with separate arbiter (from MongoDB docs) 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.

Our professional developers use NetBeans IDE, and our bug tracker is JIRA which is hosted on Atlassian. In addition, we are using BitBucket as git hosting, and is integrated to JIRA.

Recently we required to add new credit card on Amazon Web Services, and remove the old one.Amazon - no delete button for payment

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.

Background

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.

Lastly we moved our website billrun.net to Amazon and after configure Joomla, Nginx and MySQL, we received “Error displaying the error page: Application Instantiation Error” from Joomla.

One of our expertise is to give our clients high-availability products. In many solutions we are implementing different types of replication.

Our favor replication is master-master or active-active, which give the product stability and long-term life-cycle. MySQL can implement it easily, and this blog post come to give simple quick-start guide to beginners and advanced MySQL users

Background

MySQL master-master implemented as Master-Slave in dual-way, means every master think the other is slave and opposite. We will demonstrate 2 servers of replication but you can do it with 3 or more, in star topology. In addition, each master can have one or more slaves to scale reads (very recommended on master-master). 

We will implement the master-master in Amazon (AWS EC2) environment with AMI Linux distribution, but you can do it in your own environment with your favorite distribution.

SIGN UP FOR OUR NEWSLETTER NOW!

Start receiving monthly updates on new features and the latest industry trends.
Please let us know your email addresss.

DISCOVER MORE SOLUTIONS

We also offer you these services - click to learn more:

  • Number Portability Gateway (NPG)
  • Calls Generator
  • Telecom Anti-Fraud
  • And More

Read More

Download Datasheet

Find out whether you are using the best billing system available, that meets your business needs.
Please let us know your email addresss.
Invalid Input
Invalid Input

Get In Touch

 7a Derech Hashalom 

     Tel Aviv 6789208, Israel

 +1-917-7281607‎
    +353-76-6803306
    +972-58-4654666
    +44-161-3940149
    +1-914-2943161
    +972-58-5765666

 Contact Us

Company

Back To Top