EVENT PLATFORM

Abstract

In an event-driven architecture, when a service performs a task that may be of interest to other services, that service generates an event, a record of the action performed. Other services use these events so that they can perform their own necessary tasks as a result of the event. Unlike REST, the services that make the request do not need to know the details of the services that use the requests. Here's a simple example: When an order is placed on an e-commerce site, an "order placed" event is generated and then consumed by some small service. Events can be published in different ways. For example, they can be published to a queue that ensures delivery of the event to the appropriate consumers, or they can be published to the "pub/sub" template stream that publishes the event and allows access to all interested parties. In both cases, the producer announces the event and the consumer receives the event, reacting accordingly. Note that in some cases these two actors may also be referred to as publishers and subscribers. This project proposes a microservice architecture multi-tenant product for publishing targeted events. And this is to provide APIs for users to compose applications that can work with different domains.