One source, multiple targets: because it’s easy during data replication
Real-time data replication implementations cover a number of use cases that you find on this website. Amongst the most popular use cases are Real-Time Business Intelligence (real-time reporting) and High Availability. These use cases are popular because nowadays almost every organization runs into these. There is however an additional extremely popular use cases that is not typically mentioned on a real-time data replication technology website. This use case is not mentioned because the use case is not typically mission-critical and hence it gets postponed or forgotten or dealt with during “spare time”: dear DBA team, can you please refresh the data in our development/test/QA environment.
DBAs of course deal with this request all the time: take a backup of the production environment and restore it in a separate system. Optionally obfuscate the environment. Then make it available to the developers/testers. Rinse, and repeat. Most organizations don’t purchase software to support this use case because it happens somewhat rarely and hardly has to performed under time pressure. However, many DBA teams spend lots of time performing a cycle like this over and over and over again. So what if there was a technology that could help you with this?
What if there is software already in use that makes it ultra-easy to take a set of definitions and push data to another destination? Or, if data obfuscation is not part of a regular data integration scenario but it is for dev/test/QA destinations then what if the software could orchestrate these steps? Data replication software should be like that: data is already captured, and only needs to be sent to another destination.
This is where HVR stands out from many other real-time data replication technologies for two reasons:
- HVR excels in performing an initial data load. So if all that is required is to copy data in a one-time load then HVR is a great tool to use.
- HVR uses an architecture which the hub distributes all data. Many other replication technologies implement point-to-point solutions which double the amount of work going from one to two destinations, but quadruple the work if two suddenly becomes four destinations. In HVR a destination can have as many members as needed, whether that is two or twenty or two hundred.
Of course the point about organizations not purchasing software for this typically not so mission-critical use case is taken. With that said, know that if there is a (common) use case that could benefit from real-time replication software from HVR, then it can help you many other, non mission-critical use cases as well. And these other use cases can safe your DBAs a lot of time so that they can focus on other important tasks.