Abstract:
In event driven architecture, when a service does some piece of work that other services may be
interested in, that service generates a record of the done action in event-driven architecture. Other
services consume such events in order to fulfil any duties that arise as a consequence of the event.
Services that produce requests, unlike REST, do not need to know the specifics of the services that
consume the requests. Here's an easy example: When a customer places an order on an ecommerce
site, a single "order placed" event is generated, which is subsequently received by numerous
microservices. There are several methods for publicizing events. For example, they can be published
to a queue, which ensures that the event is delivered to the proper consumers, or they can be
published to a "pub/sub" model stream, which broadcasts the event and provides access to all
interested parties. In either situation, the event is published by the producer, and the consumer gets
it and reacts appropriately. It should be noted that in certain circumstances, these two players are
also referred to as the publisher and the subscriber. This project provides a multi-tenant solution
based on a micro-service architecture that would broadcast target-based events. It will also enable
APIs for users to create Apps that can function across many domains.
