Abstract: An application executing on a pod may generate a content request for a particular version of content. The application sends a request including an identifier of the version of the content to a repository in a cluster of pods. The repository determines, using the identifier, whether the version of the content is stored in the cluster or stored at a database in a different cluster. The application receives a response from the repository that may indicate that the version of the content is stored in the cluster and the response may include an identifier of a content pod storing the version of the content. The application sends the content request to the content pod storing the version of the content and may receive the version of the content without querying the database for the version of the content.

Abstract: An application executing on a pod may generate a content request for a particular version of content. The application sends a request including an identifier of the version of the content to a repository in a cluster of pods. The repository determines, using the identifier, whether the version of the content is stored in the cluster or stored at a database in a different cluster. The application receives a response from the repository that may indicate that the version of the content is stored in the cluster and the response may include an identifier of a content pod storing the version of the content. The application sends the content request to the content pod storing the version of the content and may receive the version of the content without querying the database for the version of the content.

Abstract: Techniques and solutions are described for retrieving metadata artefacts from a repository that includes multiple instances of a metadata artefact. The instances can have at least some different content. Metadata artefacts are associated with metadata describing group, searching, or selection criteria, such as one or more of a particular solution, tenant, layer, or version. A request for a metadata artefact can include at least one value for one or more of the criteria, which in turn can be used to identify one or more relevant metadata artefacts. Identifiers for, or content of, relevant metadata artefacts can be returned in response to the request. Fallback logic can be used to determine at least in part what metadata artefacts are relevant to a request, or how to return or process request results.

Abstract: Techniques and solutions are described for retrieving metadata artefacts from a repository that includes multiple instances of a metadata artefact. The instances can have at least some different content. Metadata artefacts are associated with metadata describing group, searching, or selection criteria, such as one or more of a particular solution, tenant, layer, or version. A request for a metadata artefact can include at least one value for one or more of the criteria, which in turn can be used to identify one or more relevant metadata artefacts. Identifiers for, or content of, relevant metadata artefacts can be returned in response to the request. Fallback logic can be used to determine at least in part what metadata artefacts are relevant to a request, or how to return or process request results.

Abstract: A method, a system, and a computer program product for retrieving metadata files using a local metadata index. A request to access one or more metadata files associated with at least one computing component is received. At least one primary key and at least secondary key identifying the computing component are determined. An identifier of a storage location storing the metadata files is associated with the primary key and the secondary key. A metadata index for the metadata files is generated. The metadata index includes the primary key, the secondary key, and the associated identifier of the storage location. The metadata index is stored in a memory location associated with the computing component. The stored metadata index is accessed and the metadata files are retrieved using the stored metadata index.

Abstract: A notification job is executed as a background job in a recurrent notification framework. The registered scenario along with the recurrent notification information is retrieved from a central notification scenario registration table. The user information along with an application context is retrieved from a notification scenario BADI. The user information along with a notification preference is retrieved from a user registration table. The mapping information of the user identifier and the device identifier is retrieved from the device registration table. Based on the retrieved information, the notification channel is identified from the recurrent notification information. A recurrent notification is sent through the notification channel to a device.

Abstract: Methods and system are disclosed that build or generate an enterprise mobile apps. In an aspect, a project package including multiple plugins, common functionalities, some functionalities, graphical user interface elements, etc., may be generated at a mobile application development framework (MADF). Further, the MADF may receive a request for building or generating an enterprise mobile app. The MADF may reuse the components of the project package and integrate with the application functionalities to generate a corresponding enterprise mobile app.

Abstract: A notification job is executed as a background job in a recurrent notification framework. The registered scenario along with the recurrent notification information is retrieved from a central notification scenario registration table. The user information along with an application context is retrieved from a notification scenario BADI. The user information along with a notification preference is retrieved from a user registration table. The mapping information of the user identifier and the device identifier is retrieved from the device registration table. Based on the retrieved information, the notification channel is identified from the recurrent notification information. A recurrent notification is sent through the notification channel to a device.