Architecture

This section explains the architecture of the Digital Banking Servicing Micro Apps with Microservices.

This section explains the architecture of the Digital Banking Servicing Micro Apps Without Microservices.

Architectural Components

The following are the architectural components:

Component	Description
Channel Servicing Micro Apps	Business function-specific applications that are largely reusable and efficient than monolithic applications. Each app is responsible for achieving specified business goals and has its own code base that can be developed, tested, and deployed separately.
Experience APIs	In the overall architecture of Temenos Digital, the Experience APIs are the most top-level APIs. These are the APIs exposed from Quantum Fabric to the outside world. In the Temenos world, the Experience APIs are consumed by Quantum Visualizer and used in any self-service customer application. Experience APIs are the gateways to access the resources of Temenos Digital and retrieve data in a structured way. Experience APIs determine the experience that third-party developers will get when they interact with our systems. For more information, click here.
Integration Services	Experience APIs are implemented as service-driven objects. Hence, the experience API will have a mapped integration service that executes business logic. After executing the business logic, the integration service invokes the integration template services to connect to endpoints such as Journey Manager, Transact, Core system, and Microservices
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. For more information, click here.
Spotlight	Spotlight is a web-based solution to set up and maintain customer and employee-related information and to configure the behavior of digital banking applications associated with this information. For more information about Spotlight, click here.
DBX DB	DBX DB is a MySQL based database that stores the user’s digital profile and related information. For more information about DBX DB, click here.
Transact	Transact is the Temenos Core system. It contains the user’s account information. The user is mapped as a Party. Transact contains the following modules: Customer Module: This module stores customer information. Arrangements Module: This module creates the products that are selected by the customer. The IRIS APIs are used to interact with the core system. If you use a different core system other than Transact, you must have the mentioned modules, corresponding web services for the same, and an API structure that is similar to the Transact IRIS APIs.
Third-Party Services	Any third-party services such as SMS, E-mail, and Google search components.

Application Reference Architecture

The banking application is built on application reference architecture - Model View Controller (MVC).

The application architecture includes three components - Model, View and Controller. The Model component maintains application data, and business logic. The UI/UX (View) component is the user interface of the application that displays the data. The Controller (Business Logic) component handles user's requests and render the appropriate view with Model data.

See Extension Points and Architecture for more information.