Overview
Introduction
The Originations Data Storage Microservice (ODMS) is the storage service that implements the storage features similar to those in Journey Manager. This is mainly because the requirements will come from the development of custom user Journeys and Journey Manager has been developed from many years of writing these journeys and it makes sense to learn and expand these features rather than start from scratch.
Architecture and Data Flow
Vision and Release Goal
During the life of an Onboarding Journey data is created, collected and stored - this data is often not complete and would require a temporary place of residence. An example of such data is a new Customer to the bank - as the Journey progresses additional User details are collected and stored - when the Journey is complete there will be enough information to create a new Customer in the core and the temporary data and then be purged.
The vision of the Data Storage Microservice is to build a service which can flexibly store semi-structured data for the lifetime of the journey, without a fixed view on how that data will be used. Data items will be grouped together by an key reference and searching will be supported based on metadata, or by dot notation searching within the in flight data itself. The option to enable field level validation against a defined set of rules will be available.
Each individual item of data stored will be identifiable with a Key, Name, Type and Version reference. This is not a data permanent store, lifetime will be defined when the object is created with a reminder notification (optional) will be sent out prior to the data being deleted to enable reminders to be sent. Together the Key, Name & Version will form a fully uniquely identifiable composite key for access and retrieval.
Entity Item naming conventions:
| Key (unique) | Name | Type | Version |
|---|---|---|---|
|
AGH8DX |
Txn data |
Json |
1 |
|
AGH8DX |
Txn data |
Json |
2 |
|
AGH8DX |
party1 |
Xml |
1 |
|
HJ67HJHD |
Job data |
Json |
1 |
|
HJ67HJHD |
datamodel |
Xml |
1 |
Target Audience
This is a service that offers storage function to other components of the system, it does not directly interact with end users. The expected audience for this microservice is:
- Kony Origination App which needs to store data, one use case is to support save and resume. The storage service will be accessed through the Fabric Integration Services.
- Other components in the Temenos DigitalArchitecture that have a temporary data storage need (such as Corporate Loan Origination Service),
- Operations Staff monitoring the stability and performance of the storage service through monitoring tools.
Business Value
This storage service is being built to address a missing component in the Kony stack relating to the secure temporary data storage. The primary use case is to facilitate the customer requirements to allow end users to save and resume an Origination Journey at a later date.
In this topic