airavata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gourav Shenoy (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (AIRAVATA-2338) Event-driven database replication for Apache Airavata
Date Fri, 10 Mar 2017 03:03:38 GMT

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

Gourav Shenoy edited comment on AIRAVATA-2338 at 3/10/17 3:03 AM:
------------------------------------------------------------------

We have come up with a design to perform this event-driven database replication for Apache
Airavata micro-services. The design will be as follows:

!https://ajinkya-dhamnaskar.github.io/assets/airavata_event_driven_data_replication.png|height=100%,
width=100%!


was (Author: gouravshenoy):
We have come up with a design to perform this event-driven database replication for Apache
Airavata micro-services. The design will be as follows:

!https://ajinkya-dhamnaskar.github.io/assets/airavata_event_driven_data_replication.png!

> Event-driven database replication for Apache Airavata
> -----------------------------------------------------
>
>                 Key: AIRAVATA-2338
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-2338
>             Project: Airavata
>          Issue Type: Task
>          Components: Application Catalog, Registry API
>            Reporter: Gourav Shenoy
>            Assignee: Gourav Shenoy
>            Priority: Blocker
>
> Implement an event-driven database replication for Apache Airavata. The motivation is
the fact that the current registry module (micro-service) is being refactored and broken down
to multiple independent micro-services, which includes:
> - profile-service (consisting of user, tenant and group profiles)
> - sharing-registry
> We have decided to try using different databases per micro-service, which results in
the need for replication of certain information across databases, such as user-profile or
tenant-profile. An efficient way to perform this replication is to use an event-driven approach,
which sync's contents of database via messaging events.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message