iblync · Connectors

iblync connectors: the databases, data platforms and storage it connects

Published connectors for relational databases, NoSQL, search and graph stores, Apache Spark and object storage, and custom connectors built when your system is not listed.

  • Built and supported by Interkey An Interkey product, delivered and supported by Interkey
  • One platform for migration and continuous sync The move and the replication that follows it
  • Written quote after one meeting The price is discussed in a meeting about your systems

iblync connects relational databases such as Oracle, MySQL, PostgreSQL, SQL Server and IBM Db2, NoSQL, search and graph stores such as MongoDB, Couchbase, Cassandra, Redis, Elasticsearch and Neo4j, Apache Spark, and Amazon S3 object storage. When a source or target is not listed, Interkey builds a custom connector as part of the project. Each pair is confirmed in the assessment before a quote.

Published connectors

The systems iblync connects to as a source or a target, by type, with the guide to read for each
SystemTypeRead the guide
OracleRelational databaseOracle migration
SQL ServerRelational databaseSQL Server migration
MySQLRelational databaseMySQL replication
PostgreSQLRelational databasePostgreSQL migration
IBM Db2Relational database, on LUW, z/OS and IBM iGuide not yet published
MongoDBDocument databaseGuide not yet published
CouchbaseDocument databaseCouchbase with Interkey
CassandraWide-column databaseGuide not yet published
RedisKey-value storeGuide not yet published
ElasticsearchSearch engineGuide not yet published
Neo4jGraph databaseGuide not yet published
Apache SparkData processing engineGuide not yet published
Amazon S3Object storageObject storage migration

Apache Kafka works as the bridge between systems, not as a source or a target.

Other systems

The table lists the connectors we publish. iblync also connects to systems that are not named here, and the list grows as projects need it. If your source or target is missing, do not read that as a no: send us its name and version with the form at the end of this page, and we will tell you whether a connector exists for it today or has to be built.

When your system is not on the list

Interkey builds a custom connector when a project needs one, as part of that project rather than as a separate product. An unsupported system is then a connector to build, not a reason the migration or the sync cannot go ahead.

To estimate the work, we need three things from you: the interface documentation of the system (how data is read from it and written to it), access to a test environment where the connector can be built and checked without touching production, and a sample of the data it holds. With those, the connector is scoped with the rest of the project, and it is covered in the same written quote after the meeting.

What we confirm for every source and target pair

  • Version. The exact version of the source and of the target, as they run on your side.
  • Direction. Whether each system is a source, a target or both, and whether the sync runs one way or in both directions.
  • Permissions. The access iblync needs on each side to read changes and to write them.
  • Where it runs. Where iblync runs for your project, and whether it can reach both systems from there. This is decided per project.
  • Data volume and rate of change. How much data moves once, and how much of it changes each day while the work runs.

From your list to a confirmed scope

  1. You send the source and target.

    The names and versions of the systems, the direction you need, and a rough data volume, through the form on this page.

  2. Assessment session.

    Our engineers go through each pair with your team: versions, permissions, where iblync runs and how it reaches both sides.

  3. Written scope.

    Each pair confirmed or marked as a custom connector to build, with the plan for the work and a written quote after the meeting.

What you can do once connected

02

Keep systems in step

Continuous real-time replication from the source to the target, with transfer speed you control. See real time replication.

03

Sync in both directions

Both systems accept writes and each side's changes reach the other. See bidirectional sync.

How to read this list

A name on the list means iblync connects to that system

It does not say whether the system works as a source, a target or both in your project, or which versions apply. The direction and the version are confirmed for each pair in the assessment.

See iblync at work

Two short recordings from the iblync product channel: a move into Couchbase, and a move into Amazon S3 and S3-compatible storage.

A frame from the iblync video: migrating data from SQL Server to CouchbaseData migration from SQL Server to CouchbaseVideo on YouTube, 3:19A frame from the iblync video: migrating data from SQL Server to Amazon S3Data migration from SQL Server to Amazon S3 and S3-compatible storageVideo on YouTube, 2:51

Questions about iblync connectors

Which databases does iblync connect to today?

iblync connects to Oracle, SQL Server, MySQL, PostgreSQL, IBM Db2 (on LUW, z/OS and IBM i), MongoDB, Couchbase, Cassandra, Redis, Elasticsearch and Neo4j, as well as Apache Spark and Amazon S3. It also connects to other systems on request, and Interkey builds custom connectors where a project needs them.

Can iblync connect a system that is not listed?

Yes, through a custom connector that Interkey builds as part of the project. To scope it we need the system's interface documentation and a test environment. The connector is discussed in the same meeting as the rest of the project and included in the written quote that follows.

Is every connector both a source and a target?

Not necessarily. A name on the list means iblync connects to that system; whether it acts as a source, a target or both in your project is confirmed for each pair in the assessment, together with the versions on both sides.

Does iblync work with cloud databases?

iblync connects to the engines on this list wherever they run, in your data centre or in the cloud. What is checked in the assessment is whether iblync can reach both systems from where it runs for your project, and where it runs is decided per project.

Next step

Check your source and target

Tell us the source and target systems with their versions, the direction you need and a rough data volume. We will confirm each pair, or tell you which connector has to be built.

Required field

By sending this form, you agree to our Privacy Notice.

What happens next

  1. We read your request
  2. An engineer contacts you
  3. You get an estimate or a demo
  • Built and supported by Interkey

    An Interkey product, delivered and supported by Interkey

  • One platform for migration and continuous sync

    The move and the replication that follows it

  • Written quote after one meeting

    The price is discussed in a meeting about your systems

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

or How iblync is priced

Published by Interkey. Last updated . Interkey is registered in Riyadh, Saudi Arabia under commercial registration 1010156897.