BTP Hana

The main goal is to keep your domain models clean, concise, and comprehensible by factoring out technical aspects and separating concerns.

1. A declarative paradigm using Core Data Services (CDS) to capture knowledge about problem domains.

2. A service-centric paradigm, with widespread usage of Services, Events, and Queries.

• CDS is a universal modeling language

• used to capture both static and behavioral aspects of problem domains

• conceptual, concise, and comprehensible way

• backbone of the SAP Cloud Application Programming Model.

Model Reuse provides benefits like:

• concise and comprehensible models

• interoperability between all applications

• capturing proven best practices from real applications

• streamlined data models

• optimized implementations and runtime performance.

• reusable models

• factoring out of cross-cutting or technical concerns into separate models or files,

• helps in keeping core domain models clean and comprehensible.

Common Aspects are predefined aspects ready for reuse

• "cuid,"

• "managed,"

• "temporal."

-add a universally unique primary

Localization adapts your business application to different languages to cater to specific regional markets. It is important for anything visible in the UIs.

i18n files

Localization for dynamic content is achieved by marking the attributes that need to support multiple languages with a special keyword called "localized." This creates a text table for each entity with attributes defined as "localized."

Namespaces are used to help arrive at unique names. This helps in keeping the code clean by avoiding the use of fully qualified names.

Entities represent data that can be read and written by consumers. They are uniquely identified by their primary keys. For example, Products and Suppliers can be defined as Entities.

Types describe the types of elements within entities. Various built-in types are provided, such as Integer, Decimal, and UUID. UUIDs are auto-generated IDs.

Associations capture relationships between entities. For instance, the Entity "Products" can be associated with the Entity "Supplier."

Compositions are used to model document structures through "contained-in" relationships.

For example, in the definition of "Suppliers," the "Products" composition refers to the "Products" entity.

• Associations capture relationships between separate entities

• while Compositions are used to model document structures and often indicate a "contained-in" relationship between entities.

• CDS is a technique to create persistence layer

• model is defined in .cds files during dev

• during built and deploy tables are created accordingly

• automatic migration on redeploy