Overview

Introduction

The Document Storage microservice provides the virus-free documents hosting capability for Infinity and core banking system. Under the hood, it connects the various Document Management System (Currently being Apache Sling and will be adding EFS AutoForm DM soon) and provides a set of common Apis to achieve a generic Document Storage solution that’s vendor agnostic and core agnostic.

Architecture and Data Flow

Modules

Upload Document From Temporary Location Event-driven Architecture

As a general rule, when a microservice communicates with the Document Microservice, it should go through the event stream rather than REST Api. In case of uploading a file to Document Microservice, apparently it's not feasible to send the file content directly in the event payload. The Microservice framework has created a temporary file sharing capability between Microservices which get used in this scenario. Below is the event-driven architecture to demonstrate how it works using Receipting Microservice sending receipt to Document Microservice as an example but can be easily apply to all future Micorservices who needs to upload document to the Document Micorservice.

This loosely-coupled event-driven architecture ensures the configuration over development principle when adding a new owner system in the future from the Document Microservice perspective.

Vision and Release Goal

To build a microservice which will support the upload and download of files from the user’s browser. This is to support the upload of attachment against a journey (In-flight) or hosting documents (Permanent) for the core banking system and Infinity online banking Apps. All files uploaded from the browser will be virus checked before they are persisted into the environment.

Target Audience

This microservice has the following Audiences:

1. Microservices, services which generate file-based artifacts, some of which may need to be presented to the customer.
2. Customer, the user using the Kony Origination App or Maestro form and need to upload/view a document.

Business Value

Uploading and viewing of file-based artifacts is a customer requirement to support the customer's journey. Example here may be uploading an image of a passport or a bank statement to support the application. Customers also need to be able to download a receipt as their copy of the data that they entered. Any files which are entering the cloud and can possibly be delivered to a banks system need to be secure and hence virus scanning is a mandatory requirement by most customers.