Title

CAPM - Microservice - HANA

Description

A CAP microservice works as an interface to avoid direct access to SAP HANA Cloud.

When SAP HANA Cloud artifacts (tables/views/etc) are modelled in another CAP project. The HANA Cloud instance could be both in the same subaccount or in another one.
A new CAP app could be created with the sole purpose of acting as a microservice that handles access to HANA Cloud data. Other CAP apps connect to this new CAP app rather than to HANA Cloud.
When a CAP app does not have direct access to the database layer, configuring SAP HANA cross-container access is a cumbersome task and should be avoided.
This approach simplifies consumption and maintenance as there is no need to configure HDI cross-container accesses, roles and synonyms.

Side-by-Side extensions to keep the Core Clean.
A microservice that manages user data in SAP BTP is used by multiple applications that require user information.
A microservice that manages customer loyalty data is used by multiple applications:
Customer-facing app to check their loyalty points;
- Employee-facing app to audit loyalty points accumulation;
- Supplier-facing app to create extra loyalty points campaigns;

HTML5 Application Repository Service can host any web app such as SAP Fiori, Angular, React, Vue, etc.
CAPM (Cloud Application Programming Model) apps could be developed in Node.js or Java.
Communication between the services should go through the Destination Service, not added to the diagram to simplify it.
On-premise solutions could be both SAP and non-SAP.
Cloud solutions could be both SAP and non-SAP.
SAP Cloud Identity Services is not required to connect to On-premise or Cloud solutions.

CAP, CAPM, Node.js, Java, HANA, HANA Cloud, microservice