You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@syncope.apache.org by "Mohamed Infaz (Jira)" <ji...@apache.org> on 2021/03/12 20:06:00 UTC

[jira] [Commented] (SYNCOPE-1617) Debezium integration for live sync

    [ https://issues.apache.org/jira/browse/SYNCOPE-1617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17300590#comment-17300590 ] 

Mohamed Infaz commented on SYNCOPE-1617:
----------------------------------------

Good day to you! I am interested in this project and have cloned the syncope project. I went through the codebase to get a high-level understanding of it.

I have used the Debezium framework before, and have a basic understanding of how we can convert a set of database tables, collection changes into a stream 
of events published to Kafka Topic, so that clients can then consume the events.

To scope out the project, can you please explain what you exactly meant by External Resources. Which tables or collections mean by these?

> Debezium integration for live sync
> ----------------------------------
>
>                 Key: SYNCOPE-1617
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-1617
>             Project: Syncope
>          Issue Type: New Feature
>            Reporter: Francesco Chicchiriccò
>            Priority: Major
>              Labels: gsoc2021, mentor
>
> [Debezium|https://debezium.io/] provides a mean to transform changes from RDBMS, MongoDB and Cassandra into Kafka messages.
> This tool can be leveraged to implement a listener-like approach to enable a "live-sync" mechanism from External Resources not requiring ConnId.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)