Distributed event processing architecture

1 . A system for propagating changes to a schema model, comprising:

a computer, comprising a processor and memory, and configured to propagate changes to the schema model by:

detecting a change to a system represented by the schema model;

generating a change event based on the change to the schema model;

determining one or more microservice actors that execute within a container-based computation service and are associated with content of the change event, wherein the one or more microservice actors is configured to be triggered by the change event;

dispatching the change event over an event bus to the one or more microservice actors, wherein the event bus comprises a scalable distributed event processing bus;

updating, by the one or more microservice actors, the schema model at runtime;

update a configuration of microservice actors while executing computation service;

tracking a total number of active change events and, in response to the tracking, scale up or down a number of microservice actors;

dispatching at least one further change event by the one or more microservice actors using at least one directed acyclic graph to prevent the at least one further change event from being infinitely called; and

displaying a graphical user interface (GUI) that displays one or more interactive visualizations of the schema model, wherein the one or more interactive visualizations comprise graphical elements for updating data fields of schema entities.

2 . The system of claim 1 , wherein the computer is further configured to:

detect a second change to the system represented by the schema model based on the one or more microservice actors updating the schema model; and

generate a second change event based on the second change.

3 . The system of claim 1 , wherein the change event further comprises:

identifying an object of a particular schema model that has been updated, data that has been updated, data that has been replaced or a time that an update occurred.

4 . The system of claim 1 , wherein behavior of each of the one or more microservice actors is specified by a configuration file, wherein the configuration file is associated with a particular microservice actor and specifies one or more of the following:

the name of a particular microservice actor, what objects a microservice actor can update, actions a microservice actor can take and change events that trigger a microservice actor.

5 . The system of claim 1 , wherein the computer is further configured to set up and control one or more virtual machines to execute the one or more microservice actors.

6 . A computer-implemented method for propagating changes to a schema model, comprising:

detecting, by a computer comprising a memory and a processor, a change to a system represented by the schema model;

generating, by the computer, a change event based on the change to the schema model;

determining, by the computer, one or more microservice actors that execute within a container-based computation service and are associated with content of the change event, wherein the one or more microservice actors is configured to be triggered by the change event;

dispatching, by the computer, the change event over an event bus to the one or more microservice actors, wherein the event bus comprises a scalable distributed event processing bus;

updating, by the computer, by the one or more microservice actors, the schema model at runtime;

updating, by the computer, a configuration of microservice actors while executing computation service;

tracking, by the computer a total number of active change events and, in response to the tracking, scale up or down a number of microservice actors;

dispatching, by the computer, at least one further change event by the one or more microservice actors using at least one directed acyclic graph to prevent the at least one further change event from being infinitely called; and

displaying, by the computer, a graphical user interface (GUI) that displays one or more interactive visualizations of the schema model, wherein the one or more interactive visualizations comprise graphical elements for updating data fields of schema entities.

7 . The method of claim 6 , further comprising:

detecting, by the computer, a second change to the system represented by the schema model based on the one or more microservice actors updating the schema model; and

generating, by the computer, a second change event based on the second change.

8 . The method of claim 6 , wherein the change event further comprises identifying an object of a particular schema model that has been updated, data that has been updated, data that has been replaced or a time that an update occurred.

9 . The method of claim 6 , wherein behavior of each of the one or more microservice actors is specified by a configuration file, wherein the configuration file is associated with a particular microservice actor and specifies one or more of the following:

the name of a particular microservice actor, what objects a microservice actor can update, actions a microservice actor can take and change events that trigger a microservice actor.

10 . The method of claim 6 , further comprising:

setting up and controlling, by the computer, one or more virtual machines to execute the one or more microservice actors.

11 . A non-transitory computer-readable medium embodied with software for propagating changes to a schema model, the software when executed configured to:

detect a change to a system represented by the schema model;

generate a change event based on the change to the schema model;

determine one or more microservice actors that execute within a container-based computation service and are associated with content of the change event, wherein the one or more microservice actors is configured to be triggered by the change event;

dispatch the change event over an event bus to the one or more microservice actors, wherein the event bus comprises a scalable distributed event processing bus;

update, by the one or more microservice actors, the schema model at runtime;

updating a configuration of microservice actors while executing computation service;

tracking a total number of active change events and, in response to the tracking, scale up or down a number of microservice actors;

dispatch at least one further change event by the one or more microservice actors using at least one directed acyclic graph to prevent the at least one further change event from being infinitely called; and

display a graphical user interface (GUI) that displays one or more interactive visualizations of the schema model, wherein the one or more interactive visualizations comprise graphical elements for updating data fields of schema entities.

12 . The non-transitory computer-readable medium of claim 11 , wherein the software when executed is further configured to:

detect a second change to the system represented by the schema model based on the one or more microservice actors updating the schema model; and

generate a second change event based on the second change.

13 . The non-transitory computer-readable medium of claim 11 , wherein the change event further comprises identifying an object of a particular schema model that has been updated, data that has been updated, data that has been replaced or a time that an update occurred.

14 . The non-transitory computer-readable medium of claim 11 , wherein behavior of each of the one or more microservice actors is specified by a configuration file, wherein the configuration file is associated with a particular microservice actor and specifies one or more of the following:

the name of a particular microservice actor, what objects a microservice actor can update, actions a microservice actor can take and change events that trigger a microservice actor.