Overview of Event Store
This section provides you an overview and uses of the Event Store microservice.
Event Store supports event-driven architecture of Temenos Microservices. In the event-driven interfaces, all microservices raise events to Event Store.
Event Store is a microservice, which helps you to
- Record all the events as a part of their Inbox events and raises those events to the respective microservice using the Outbox infrastructure
- Store the data as a series of immutable events over time
- Record all events happen in each of the microservices
- Forward the raised events to the respective microservice
Events can be various types as shown below:
- Command Processed Event
- Business Event
- Command Event
Each event has a well-defined schema. Microservice raises events, which are compliant to the event schema.
To simplify the routing of events, Event ID should be in a standard convention as shown below.
Event Name Convention: <MS Service Name>.<Operation Id>
Event name : FundReservation.ReserveFund
Where,
- Fund Reservation is the microservice name
- ReserveFund is the operation supported in the microservice
This microservice provides the following services:
- A persistent store of internal events that ensures ordering and uniqueness of events
- History or audit log
- Allows replay and catch-up
This microservice provides the following features:
Event Store Management API Interface
Event Store Service provides a centralized configuration service supported across applications to manage their configurations using API-based interface. This microservice supports distributed deployment and provides a stateless API interface. It has a data store (database) to persist configurations uploaded through the API interface.
Versioned Artifact
Every configuration file in the configuration microservice is maintained as a versioned artifact. Under each configuration group, applications are allowed to maintain more than one configuration content using a unique Config name.
Get Configuration API
- Get Configuration based on Config Name: Get configuration file based on the group name and configuration where version ID is not a mandatory. If the version is not sent, then client receives the latest version for the configuration file content.
- Get List of Configurations managed under a Configuration Group: It provides the list of latest configuration names managed under the provided configuration group.
Addition of a new Artifact
The POST API allows the application to add a new configuration content under a given configuration group along with the associated version ID. If the version input is not provided, microservice automatically creates or increments the version.
Modification of an existing artifact
The PUT API allows the client application to update the file content to the existing configuration content. If the version is not provided, the latest version for the configuration content gets updated.
In this topic
