While the detailed discussion on this topic is beyond the scope of this book, it makes logical sense to briefly look at what these mean before we get into the nitty gritty of configuring the two using Trove.
Please do remember that this is a general understanding and certain advanced features provided by some database engines may follow a different pattern.
Replication defined in the simplest terms is the process of keeping a copy of the data available on another node. Replication typically has two or more nodes, where one is the master (where reads and writes happen) and the others are slaves (where only reads can happen). There are concepts of master-master replication, but that's beyond the scope of this book.
There are two main reasons/benefits for which one could opt for replication:
For failover (Business Continuity Plan):
In the event the master fails, the slave can be promoted and the applications can continue to work
The failover is mostly manual...