EVENTPUB

Abstract

In event-driven architecture, when a service performs a task that other services may be interested in, it generates an event, which is a record of the action. These events are consumed by other services so that they can complete any duties necessitated by the occurrence. In contrast to REST, services that generate requests do not need to know the specifics of the services that consume them. Here's a simple example: When a customer places an order on an ecommerce website, a single "order placed" event is generated and processed by several microservices. It is possible to publish events in a variety of methods. For instance, they can be published to a queue that ensures delivery of the event to the proper consumers, or they can be published to a "pub/sub" model stream that publishes the event and provides access to all parties with an interest. In either scenario, the producer publishes the event, and the consumer receives and responds appropriately to that event. In some instances, these two parties may also be referred to as the publisher and the subscriber. This project provides a microservice-based, multi-tenant product for publishing target-based events. And it will enable APIs for users to create Apps that are compatible with multiple domains.