​
TL;DR

We are faster, way faster. This allows you to have an order of magnitude shorter downtime when migrating your application from one infrastructure to another or to refresh your OLTP data in the Data Warehouse, so you can analyze the data quicker.
Please check our extract and load benchmarks and replication benchmarks

​
Background

Since the advent of computers data has been a critical component of the infrastructure and technologies have evolved to store and retrieve data in a performant container while keeping costs low. We have seen the rise of RDBMS databases, NoSQL databases and now we are in the Cloud database era that promises infinite scalability and elasticity. Part of the problem is moving this data from one platform to another. Given that data volumes have exploded and applications have significantly shorter downtime SLAs, this problem has become the brunt of failures of most data migration projects.
60% to 80% of data migration projects fail.
Wirekite solves this problem, albeit better than other technologies.

​
Data Migration

Consider a 100 GB table and a data migration solution that moves data at 10 MBPS (the average speed of other solutions), you will take approx 22 hours to transfer the data. If the rate is amped up to 100 MBPS, it will take slightly more than 2 hours to move the same amount of data. Now imagine if the rate is 1 GBPS (wirekite), you can do the migration in 20 minutes.
The data transfer rate is not limited by the network but by the rate of data extraction, loading on source and target database.

​
Data Warehouse Pipeline

Imagine the same kind of performance impact when you can move all of the data from your production OLTP database into your Data Warehouse. When you have the “recent” data faster, your analysis is far more accurate and valuable.

​
Performance

​
Extract and Load / Data

One of the first stages of any data migration project is moving data to the target database. This involves extracting all the data and loading into the target database. Since the data does not have to be inserted in any given order in the target database, we can take advantage of large degree of parallelism.

​
Replication / Change

Once the data is loaded to the target database wirekite makes sure that continuous changes that are happening in the source database are replicated to the target database. Note that changes happen on the source database in a given order and must be executed in the same order on the target database, thus preventing us from using parallelism. Wirekite handles the single threaded replication very efficiently.