Data change controller

A method of supporting synchronisation of a first data set and a second data set stored in a data repository, the method comprising the steps of:

• triggering, by the data repository, in response to a commit order relating to an ongoing transaction requested by a client and instructing the data repository to apply one or more data modifications on the first data set, transmission of a notification event message relating to the ongoing transaction to a data consistency controller;
• receiving, by the data repository, a notification event response message relating to the ongoing transaction from the data consistency controller, the notification event response message indicating to the data repository whether
• to commit the one or more data modifications instructed by the commit order on the first data set and one or more corresponding data modifications on the second data set, or
• to roll back the one or more data modifications instructed by the commit order on the first data set;
• and
• receiving, by the data repository, one or more request messages relating to the ongoing transaction from the data consistency controller, the one or more request messages requesting the data repository to apply one or more additional data modifications on the first data set and one or more corresponding additional data modifications on the second data set.

A method of controlling synchronisation of a first data set and a second data set stored in a data repository, the method comprising the steps of:

• receiving, by a data consistency controller, a notification event message triggered by the data repository in response to a commit order relating to an ongoing transaction requested by a client and instructing the data repository to apply one or more data modifications on the first data set;
• transmitting, by the data consistency controller, a notification event response message relating to the ongoing transaction to the data repository, the notification event response message indicating to the data repository whether
• to commit the one or more data modifications instructed by the commit order on the first data set and one or more corresponding data modifications on the second data set, or
• to roll back the one or more data modifications instructed by the commit order on the first data set;
• and
• transmitting, by the data consistency controller, one or more request messages relating to the ongoing transaction to the data repository, the one or more request messages requesting the data repository to apply one or more additional data modifications on the first data set and one or more corresponding additional data modifications on the second data set.

A data repository for supporting synchronisation of a first data set and a second data set stored in the data repository, the data repository comprising:

• a triggering component configured to trigger, in response to a commit order relating to an ongoing transaction requested by a client and instructing the data repository to apply one or more data modifications on the first data set, transmission of a notification event message relating to the ongoing transaction to a data consistency controller;
• and
• a receiving component configured to:
• receive a notification event response message relating to the ongoing transaction from the data consistency controller, the notification event response message indicating to the data repository whether
• to commit the one or more data modifications instructed by the commit order on the first data set and one or more corresponding data modifications on the second data set, or
• to roll back the one or more data modifications instructed by the commit order on the first data set;
• and
• receive one or more request messages relating to the ongoing transaction from the data consistency controller, the one or more request messages requesting the data repository to apply one or more additional data modifications on the first data set and one or more corresponding additional data modifications on the second data set.