All Classes and Interfaces
Interfaces
Class
Description
The broker config resolver component is in charge of providing the proper broker configuration (i.e.
The event consumer handles
RepoEvent objects, usually to publish them again in a different output channel.Registry that manages all the
EventConsumer objects of the event gateway microservice.Predicate definition for the class
RepoEvent to be able to define event filters that check different conditions in the corresponding events (i.e.The event filter factory has the responsibility of creating new event filter objects taking into account the specification provided by the client using a
Subscription object.The
GatewayEventConsumer forwards the RepoEvent to the event router that uses the EventConsumerRegistry to subsequently send the
event to the corresponding EventConsumer/s.The event subscription component is in charge of publishing the events consumed from ACS to other channels.
The event subscription factory has the responsibility of creating new event subscription objects taking into account the specification provided by the client
using a
Subscription object.Registry that manages all the
EventSubscription objects of the event gateway microservice.Service in charge of dealing with the internal logic of the gateway
The event transformation component is in charge of transforming the content of a
RepoEvent instance.The gateway event consumer is the main entry point of the event gateway microservice.
The subscription publisher is the component in charge of publishing the
RepoEvent objects to the corresponding channels.The subscription publisher factory has the responsibility of creating new subscription publisher objects taking into account the specification provided by
the client using a
Subscription object.