Skip to main content
Version: 13.x (Current)

Connectors Overview

This page describes how to connect your data infrastructure to the Fast Data services.

Overview​

Fast Data uses an event streaming platform to ingest in near real-time all the messages regarding changes occurring within your systems (e.g. create, update or delete operations). Depending on how changes are produced, where your source data is stored and how they can be accessed there can be different ways to produce the corresponding change event on the Fast Data ingestion topics. The components in charge of transmitting the changes from your systems to the event streaming platform are generally known as Connectors.

When data is stored on a database and the changes to be monitored are the action on the database itself, exploiting a Change Data Capture (CDC) system is usually recommended. This system works by detecting changes in the database and emitting the corresponding events in near real-time on the configured event streaming platform so that subsequent components can process the events. Examples of databases on which a CDC can be instantiated are:

note

The complete list of supported databases can be found in Debezium documentation.

How to connect any data source to Fast Data​

In general, any application that writes messages onto an event messaging platform adopting one of the formats accepted by the Real-Time Updater can act as a Connector. In particular, it is possible to either write your own custom Connector tailored for your unique needs and requirements, or use one of the Connectors available in the Mia-Platform Marketplace.

Some connectors you'll find in the Marketplace:

Change Data Capture Systems​

There are different ways to set up a CDC system between your data source and the event messaging platform from which Fast Data ingests messages. In the following paragraphs we explain the main paths currently available.

Bring Your Own CDC​

Set up your own Change Data Capture system within your infrastructure so that you can maintain the control on who can access your data source and customize its settings depending on your specific use case and environment.

This approach has already been tested, verified and it is working in production with the following Change Data Capture software:

Change Data Capture systems described above publish change events in one of the formats supported by Fast Data. When another CDC system is employed it is important to either verify that such component can produce compatible messages or provide a custom message adapter to the Fast Data Real-Time Updater component. In this way Fast Data can easily process change events employing user-defined formats.

danger

When configuring any CDC you have to bear in mind that Fast Data needs the whole record in every message sent. This may look worse storage-wise but it allows the microservices to save precious time on MongoDB queries that would otherwise slow down the process considerably.

Managed Debezium CDC​

Debezium is an open-source distributed platform for change data capture. It can be either deployed as a Kafka Connector on the Kafka Connect framework, when employing Apache Kafka as event streaming platform or as a standalone service. In Mia-Platform Marketplace it is possible to find different version of Debezium Server, one for each supported database, which can be used as plugin or template with an almost ready-to-use configuration. More details can be found in the dedicated Debezium Server configuration page.