A.Events

B.API management

C.Containers

D.Microservices

E.Continous delivery

A.Separation of application code and runtime configuration

B.Stateless and self-contained application processes

C.Multiple codebases tracked in revision control, single deploy

D.Traceability and reproducibility of all changes

E.Unite build and run stages

A.DDIC fields, structures and tables

B.SOAP services for internal and external access

C.CDS Views

D.SAP Fiori UIs for custom business objects

A.Highly productive development with the SAP Business Application Studio and SAP S/4HANA Cloud Platform SDK.

B.Support for hybrid scenarios

C.De-coupled integration via APIs, events, and replication services

D.Separated application stacks.

E.Lifecycle-dependent

A.Identifies the provider implementation inside an event source system. For example, a provider for business events in SAP S/4HANA could use the value BO to represent business objects events. A provider for technical events inside SAP S/4HANA Cloud could choose the value TECH.

B.Identifies the source system of an event type, for example S4H would represent an SAP S/4HANA Cloud system with the system ID S4H

C.Identifies the event type. In SAP S/4HANA Cloud, the event type mostly contains the respective object type to which the event belongs.