TRIGGER PUBLISHER

Abstract

When a service in an event-driven architecture completes a task that other services might find interesting, that it creates an event, which serves as a record of the action that was completed. Other services use such events as a resource to carry out any duties that become necessary as a result of the event. Services that make requests, unlike REST, do not have to be aware of the specifics of the services consuming the requests. Here's an example: A single "order placed" event is generated and then consumed by numerous microservices when an order is placed on an e-commerce website. Various methods can be used to publish events. For instance, they can be broadcast to a queue that ensures delivery of the event to the right consumers or to a stream using the "pub/sub" architecture, which publishes the event and makes it accessible to everyone who is interested. In either scenario, the event is published by the producer, which the consumer then gets and responds to. These two parties might alternatively be referred to as the publisher and the subscriber in various situations. This project suggests a multi-tenant solution that publishes target-based events using a micro-service architecture. Additionally, it will offer APIs so that users may create apps that can function in other domains.