Introduction to Microservices

Microservices is an architectural style that structures an application as a collection of small autonomous services, modeled around a business domain. Each service is self-contained and implements a single business capability.

Microservices can be reused in more than one different process or over different business channels. These services exist as independent artifacts, that can be scaled without any dependence on other microservices.

Characteristics of Temenos Microservices

Temenos Microservices contains the following characteristics

  • Designed to support high volume, distributed, and low latency business requirements.
  • Provides a design choice of choosing the database type (SQL/NoSQL).
  • Provides a secure private data storage.
  • Each individual Microservice contains its own data storage.

Microservices vs Transact vs Technology

The following table provides the list of microservices with information on the supported database type and if ingestion is required.

Microservice Database Type Ingestion Required
Party NoSQL Yes
Marketing Catalog NoSQL Yes
Due Diligence NoSQL No
Originations Data Storage NoSQL No
Document Storage SQL No
Arrangement SQL Yes
Holdings NoSQL Yes
Consents SQL No
Service Request NoSQL No
Campaign SQL No
Aggregation SQL No
Notifications (Alerts)   No
Origination Processing NoSQL No
Savings Pot NoSQL No
Organisation Reference Data Structure NoSQL No
Event Store SQL No
Adapter Framework NoSQL No
Generic Config NoSQL No

Receipt Microservice is discontinued from 22.04 release. The document generation capability is now handled by Formpipe, a third-party tool, through Document Storage Microservice.

  • Party – Ingestion is supported out of the box across all releases from R17 AMR release of T24/Transact.
  • Marketing Catalog – Supported across all releases from R17 AMR, but only for AA products. Legacy products like LD, MM, MG, and other similar are required for L3 customization.
  • Arrangement – Supported across all releases from R17 AMR for AA product line like – Account, Lending, Deposits, and Portfolio.
  • Holdings – Supported across all releases from R17 AMR of T24/Transact.

Note that, if the non-Transact core does not support ingestion, then the implementation team can directly implement with their core banking system.

Events Details for Infinity Microservices

This section provides the details about all the events available as part of Infinity Microservices wherever applicable. In addition to this, the Provider and the Consumer details of those events are also available.

Event Topic Name – Event Topic Name represents the topics used by the microservice irrespective of microservice is Provider or Consumer. The Provider and Consumer columns provide the actual provider and consumer details.

Microservices Event Topic Name

Provider 

(DES/ MS/ any other)

Consumer

(MS/any other) 

Document

document-inboxdocument-outbox

Document MS Event Store MS
document-event-topic Event Store MS Document MS (Internally it will call Document Management System)
Originations Processing (Corporate LOS)

ms-corporatelos-inboxms-corporatelos-outbox

Originations Processing (Corporate LOS) Event Store MS
ms-corporatelos-event-topic Event Store MS Adapter MS
Origination Data Storage

storage-inbox

storage-outbox
ODMS Event Store MS
storage-event-topic Event Store MS Adapter MS
Party 

ms-party-inboxms-party-outbox

Party MS 

 

Event Store 
ms-party-event-topic Event Store MS Adapter MS

table-updateerror

DES Party MS
Marketing Catalog table-updateerror DES Marketing Catalog MS
Arrangement

external-account-event

Account Aggregation MS Arrangement MS
context-event Arrangement MS Account Aggregation MS
assembled-event DES Arrangement MS
Holdings

external-holdings-event

Account Aggregation MS Holdings MS
context-event Holdings MS Account Aggregation MS
assembled-event DES Holdings MS
Account Aggregation

context-event

Account Aggregation MS Arrangement/Holdings MS
external-account-event Account Aggregation MS Arrangement MS
external-holdings-event Account Aggregation MS Holdings MS
notification-event Account Aggregation MS Notification (Service Adapter)
Service Request acknowledgement-event Service Request Fabric App Service request MS
order-event Service request MS Service Request Fabric App
Notification (Service Adapter) notification-event Account Aggregation MS Notification (Service Adapter)

For information about the Revision History, click here.


Field Name
|
Application/Table name

Temenos Headquarters SA
2 Rue de l'Ecole-de-Chimie
CH - 1205 Geneva
Switzerland

Copyright © 2020- Temenos Headquarters SA

Published on :
Tuesday, May 23, 2023 9:31:50 PM IST