The database vendor's own tool
Suits: copies and moves inside one vendor's products, with that vendor's support.
The real cost: it usually stops at the vendor's own boundary, so a second engine needs a second tool.
iblync · Comparing replication tools
Ten criteria that separate one data replication tool from another, the questions to ask each vendor, and how iblync answers them.
Published 7 min read
Data replication tools copy changes from one database to another and keep the two in step. They differ less in what they copy than in how they are licensed, who operates them, where they run and how they are supported. This page gives ten criteria and nine vendor questions for a Saudi buyer, and shows how iblync, built by Interkey, answers each.
| Criterion | Why it matters | What to ask | How iblync answers |
|---|---|---|---|
| Who makes it | Whoever builds the tool and stands behind it is who you call when a job stops | Where is the vendor based, and who represents it locally? | Interkey, a Saudi technology company in Riyadh |
| Licensing model | The licence terms shape the budget for every source you add later | By server capacity, by number of sources, or by volume? | Discussed in a pricing meeting, with a written quote after it |
| Who runs the tool | A tool nobody on your side has time to run tends to stall after the first migration | Your team or the vendor's team? | Delivered with the Interkey team that operates it; no development team needed on your side |
| Local support | Replication problems show up in production, where a clear answer in your own language counts | In which language is support given, and by whom? | From Interkey, in Arabic and English |
| Where it runs | Where the data may go often decides the choice before price does | Does any data leave the Kingdom? | Decided per project before design |
| Sources and targets | An unsupported version found late in a project means a delay or a rewrite | Is my exact system version supported today? | The current list is on the iblync connectors page |
| Custom connectors | Few estates use only the systems on a vendor's list | What if my system is not on the list? | Built when needed, as part of the project |
| Two-way synchronisation | When both sides accept writes, a record changed in both places needs a rule | How is a conflict handled? | Supported |
| Load control on the source | Replication that competes with users slows the business down | Will production be affected? | Transfer speed and resource use can be limited |
| Reporting | Regular reports show that replication is complete without someone checking by hand | Which regular reports will we receive? | Weekly and monthly replication reports |
Ask every vendor the same ten questions, ourselves included, and ask for the answers in writing against your own systems rather than a general product sheet.
Suits: copies and moves inside one vendor's products, with that vendor's support.
The real cost: it usually stops at the vendor's own boundary, so a second engine needs a second tool.
Suits: moves between different engines, and keeping two systems in step while both stay live.
The real cost: the licence is only part of it. Someone has to configure, watch and support the platform, so ask who.
Suits: moves into that provider's own managed databases.
The real cost: its fit for targets outside that cloud, and whether data leaves the Kingdom on the way.
Suits: teams with engineers who will build the pipeline and maintain it.
The real cost: the people who build it, run it in production and own it once the project ends.
The same nine questions for every tool on your shortlist, answered in writing.
Most replication tools are sold as a licence: you buy the right to use the software, and your team installs, configures and runs it. Some are delivered with the team that runs them, and what you buy is the result. Four differences decide which suits you. With a licence:
A replication tool runs inside your production estate, so the questions about support and location come before the questions about features. Ask every vendor in which language support is given, who answers, and which hours it covers in your time zone. iblync is supported by Interkey, in Arabic and English.
Where the platform runs, and whether any data leaves the Kingdom, is decided for each project before the design starts, not after the first job runs. Write the answer into your evaluation next to the source and target versions, so every vendor is held to the same condition. Our guide to data residency in Saudi Arabia covers how to choose the location.
Three or four tools that pass the ten criteria on paper, with each answer in writing.
The same representative sample for every vendor, including Arabic text, dates and numeric precision, with the acceptance checks agreed beforehand.
Each candidate runs next to your current setup on that data, with the load on production limited and measured.
Every vendor scored against the same criteria. Our data replication evaluation guide carries the scorecard.
iblync is a platform built by Interkey for migrating and synchronising data between systems that were not designed to exchange it, and it is delivered with the team that operates it. It fits when you need a one-off or phased migration followed by continuous sync, when both systems accept writes and must stay in step in both directions, when the load on a production source has to be limited, or when one of your systems needs a custom connector. If the target stops, changes wait in a queue and are processed when it returns. Work is set up as low-code workflows rather than scripts written for each project, and no development team is needed on your side.
It does not fit every case. When the database vendor's own tool already covers your move, use that tool: it is usually the simpler path, and we will say so. And if your team wants a tool it installs and runs itself, with no vendor team beside it, iblync is not built for that way of working.
Relatediblync
A data replication tool is software that carries changes from one database to another, continuously, so the two systems stay in step. Most tools first copy the existing data once, then apply each insert, update and delete as it happens. Teams use them for migrations with little downtime, for reporting copies and for keeping two systems live side by side.
Change data capture is the method of finding out what changed in the source; replication is delivering that change to the target. A replication tool usually relies on change data capture, by reading the database log, by triggers or by queries, and then applies the changes in order. Our change data capture guide explains each method and what it asks of the source.
Relatedchange data capture guide
Vendors use three common models: by server capacity, by number of sources, or by data volume. Ask which one applies before you compare figures, because the three do not compare directly. For iblync, the price is discussed in a meeting, followed by a written quote; you can ask for that meeting through the form on this page.
The one that answers the ten criteria above for your own case. For most Saudi organisations two of them weigh most: local support in your language, and where the tool runs and whether data leaves the Kingdom. Ask every vendor on the shortlist to answer both in writing, next to your exact source and target versions, and score them all the same way.
Some do. iblync supports synchronisation in both directions, where both systems accept writes and stay in step. Ask every vendor how a conflict is handled, that is, what happens to a record changed on both sides at once, because that rule is a design decision made before the first job runs.
Yes. iblync is delivered with the Interkey team that operates it, so the jobs are configured, watched and supported by Interkey rather than handed over as a licence. No development team is needed on your side. Your team keeps the decisions: what moves, when to switch, and which checks prove the result.
Next
Next step
Tell us your source and target systems and versions, the rough data volume, and whether data must stay in the Kingdom. The price is discussed in a meeting, followed by a written quote.
What happens next
Or directly
+966-11-2180999 [email protected]Tawuniya Towers, North Tower, 7th Floor, King Fahad Highway, Olaya, P.O. Box 56835, Riyadh 11564, Saudi Arabia