Define architecture where/when synchronization is managed between the different information "stores"

10826
Reporter: mdoering
Type: Task
Summary: Define architecture where/when synchronization is managed between the different information "stores"
Priority: Critical
Resolution: Fixed
Status: Closed
Created: 2012-02-16 11:23:35.883
Updated: 2013-12-16 17:50:41.527
Resolved: 2013-12-10 16:20:23.653
        
Description: For example when a single organization record changes in the registry we will need to update at least the following components:
 - registry db
 - solr index
 - flush ws cache

We need to think about where this happens and how it is triggered. Do we rely on the event system for this and the above will become listeners to queues? Will we embed things into the service api code? How can we make sure all our applications are not bypassing this, for example by using the persistence layer directly when the above service layer evokes events or does the synchronization.]]>
    

Author: kbraak@gbif.org
Created: 2013-12-10 16:20:23.684
Updated: 2013-12-10 16:20:23.684
        
The Registry2 has a built-in event broadcasting system. A dataset update will trigger a message, listened to by the crawler and the built-in SOLR index for example.

Closing issue.