Abstract: Methods and systems are used for providing a generic command line interface to an extensible list of cloud platform services. As an example, a generic command request including a command and command input data is received, by a command line interface (CLI) backend, from a client. A platform service for the command is determined, by the CLI backend, based on command metadata associated with the command. The command input data is mapped, by the CLI backend, to a platform service application programming interface (API) associated with the platform service based on the command metadata associated with the command. The platform service API is called, by the CLI backend, based on the mapping. Response data from the platform service API is mapped to command output data in a generic command response based on the command metadata associated with the command. The generic command response is transmitted to the client.

Abstract: A Tenant request to subscribe to an Application is received. A Service that the Application consumes is determined. The Tenant is determined to be new to the Service. In response to determining the Tenant is new, a subscription of the Tenant is provided in the Service, and the Application is added to the subscription.

Abstract: A system may include a shared storage data store containing a first version of entities with original content and a local tenant storage data store to contain information associated with a tenant's application server. A database interface agent may enter a copy-on-access mode and maintain materialization and modification flags. The agent may then initiate an upgrade process during which the first version of the entities are utilized by the application server. The agent may then enter a copy-on-write mode and delete, from the local tenant storage data store, entities having flags that indicate the table was migrated but did not receive customer data. The structure of the remaining entities may then be updated in view of the structure of the second version of the entities. Finally, the content of the entities may be updated in view of the content of the second version of entitles and previously received customer data.

Abstract: Various examples are directed to systems and methods for configuring an application that uses a plurality of microservices. A distributed configuration deploy service (DCDS) may generate a first set of microservice configuration parameter values for a first microservice of the plurality of microservices based at least in part on a first microservice configuration model for the first microservice and at least in part on a second configuration model for a second microservice of the plurality of microservices. A configuration application programming interface (API) may determine that the first set of microservice configuration parameter values do not conflict with first live data at the first microservice. The configuration API may also lock the first microservice; apply the first set of microservice configuration parameter values to the first microservice; and release the locking of the first microservice.

Abstract: A development maintenance (Dev-Maintain) computing system is upgraded from a release version n to a release version n+1, where a production (Prod) computing system is on the release version n, and a development preview (Dev-Preview) computing system is on the release version n+1. Changes are transported from the Dev-Preview computing system to the Dev-Maintain computing system. Inactive changes transported from the Dev-Preview computing system into the Dev-Maintain computing system are merged to generate merged changes. The merged changes are transported to the Dev-Preview computing system. A release version upgrade is performed to the Prod computing system and to the Dev-Preview computing system. Active changes are transported from the Dev-Maintain computing system to the Prod computing system.

Abstract: A Tenant request to subscribe to an Application is received. A Service that the Application consumes is determined. The Tenant is determined to be new to the Service. In response to determining the Tenant is new, a subscription of the Tenant is provided in the Service, and the Application is added to the subscription.

Abstract: Methods, systems, and computer program products for accessing a database element are described. A table link of a persistency interface is defined, the table link being a representation of a table of a persistency schema. A role for the persistency interface is defined, the role defining a type of access for a specified portion of the database element.

Abstract: Methods and systems are used for using services in stacked services. As an example, a first service instance of a first service bound to a first application is instantiated. A second service instance of a second service is instantiated from within a first service broker. The second service instance is bound to the first service to be used indirectly in a context of the first application. A subaccount of the first application is provided to the second service as a first consumer. A third service instance of a third service is instantiated from within a second service broker. The third service instance is bound to the second service to be used indirectly in a context of the first application. The first application uses the second service indirectly through the first service. The subaccount of the first application is provided to the third service as the first consumer.

Abstract: A Proxy Service Broker on a Hoster Platform as a Service (PaaS) receives a request for a Service Catalog including PaaS services available from a Partner PaaS. Using the Proxy Service Broker, creation of an instance of a Partner PaaS service selected from the Service Catalog is initiated. Using the Proxy Service Broker, a call is transmitted to a Partner Service Broker on the Partner PaaS to create the instance of the Partner PaaS service executing on the Partner PaaS. An Application is deployed on the Hoster PaaS to consume the instance of the Partner PaaS service. The deployed Application is bound with the instance of the Partner PaaS service and directly consumes the bound Partner PaaS service.

Abstract: Methods and systems are used for using services in stacked services. As an example, a first service instance of a first service bound to a first application is instantiated. A second service instance of a second service is instantiated from within a first service broker. The second service instance is bound to the first service to be used indirectly in a context of the first application. A subaccount of the first application is provided to the second service as a first consumer. A third service instance of a third service is instantiated from within a second service broker. The third service instance is bound to the second service to be used indirectly in a context of the first application. The first application uses the second service indirectly through the first service. The subaccount of the first application is provided to the third service as the first consumer.

Abstract: A mesh-type scaler is selected for performing overall mesh-wide scaling of a microservices mesh. The microservices mesh is scaled with the mesh-type scaler and one or more mesh scaling rules to generate a predicted value for a monitoring parameter of one or more monitoring parameters. A single-service-type scaler is selected. The monitoring parameter is measured with the single-service-type-scaler to generate a measured value. For an individual service associated with the microservices mesh, a target value is calculated for the monitoring parameter using the predicted value and the measured value. The target value is compared against a defined threshold to generate a scaling value used to determine if scaling is needed with respect to the individual service.

Abstract: An IoT data packet of IoT data in a first data format is received over a distributed system from an Internet of Things (IoT) device. A determination is made that a second different data format of at least some of the IoT data is being used by at least one application by using an IoT data model of an IoT persistency service storing the IoT data in different data formats supporting different applications. A transformation rule in the IoT data model is used to transform the IoT data packet in the first data format to the second different data format. The IoT data packet in the second different data format is stored in the IoT persistency service.

Abstract: Various examples are directed to systems and methods for configuring an application that uses a plurality of microservices. A distributed configuration deploy service (DCDS) may generate a first set of microservice configuration parameter values for a first microservice of the plurality of microservices based at least in part on a first microservice configuration model for the first microservice and at least in part on a second configuration model for a second microservice of the plurality of microservices. A configuration application programming interface (API) may determine that the first set of microservice configuration parameter values do not conflict with first live data at the first microservice. The configuration API may also lock the first microservice; apply the first set of microservice configuration parameter values to the first microservice; and release the locking of the first microservice.

Abstract: A deployment infrastructure (DI) imports at least one object description artifact and at least one content data file associated with a database object to a design-time container. The DI deploys the database object in a runtime container based on the at least one object description artifact and the at least one content data file. The DI exports the at least one object description artifact in the design-time container and at least one updated content data file based on an updated database object in the runtime container, wherein the updated database object includes updated content of the database object generated at runtime of a database application.

Abstract: Implementations of the present disclosure include methods, systems, and computer-readable storage mediums for test optimization based on actual use of configuration parameters. Actions include receiving a parameter set from a monitoring system, the parameter set including multiple configuration parameters corresponding to development artifacts detected by the monitoring system, retrieving statistical data from a central data analysis infrastructure, the statistical data being retrieved from application systems executing software created out of the development artifacts, processing the parameter set using the statistical data to generate parameter clusters, and providing the parameter clusters to an integrated development environment to generate a test scope proposal based on the parameter clusters.

Abstract: Implementations of the present disclosure include methods, systems, and computer-readable storage mediums for concurrent production use of an application and training of a modified application. Actions include receiving a change request that provides at least one application change for an application executed by a production system, retrieving, from the production system, a portion of production data associated to the at least one application change, executing training of a model of the application using the one or more production data to generate a trained model of the application, testing the trained model of the application to generate test results, extending the change request by adding the trained model, and providing, by the production system, the extended change request to deploy the at least one application change and the trained model to the production system.

Abstract: A request is received at a service manager from a service broker proxy or a service manager aware service registry to create a service instance. Creation of a service instance is requested from a service broker. Details of the created service instance are stored within the service manager. A success or failure status is returned to the service broker proxy.

Abstract: A request is received from a deployer associated with an application to create an instance broker service instance. A request is received from the deployer to bind the instance broker service instance to the application. Instance broker credentials associated with the instance broker service instance are received and provided to the application. The application uses the instance broker credentials to access the instance broker service instance and determines whether to create a new service instance using the instance broker service instance.

Abstract: A development maintenance (Dev-Maintain) computing system is upgraded from a release version n to a release version n+1, where a production (Prod) computing system is on the release version n, and a development preview (Dev-Preview) computing system is on the release version n+1. Changes are transported from the Dev-Preview computing system to the Dev-Maintain computing system. Inactive changes transported from the Dev-Preview computing system into the Dev-Maintain computing system are merged to generate merged changes. The merged changes are transported to the Dev-Preview computing system. A release version upgrade is performed to the Prod computing system and to the Dev-Preview computing system. Active changes are transported from the Dev-Maintain computing system to the Prod computing system.

Abstract: At an Operational Insights and Development Recommendation (OIDR) system, development artifacts from a central artifacts repository are received. At the OIDR system, statistical data from a central data analysis infrastructure is received. The statistical data is retrieved from application systems running software created from the development artifacts, and the statistical data is correlated with the development artifacts. Data insights and recommendations based on the correlated statistical data and development artifacts are provided by the OIDR system to an enhanced integrated development environment (IDE). Recommendations are derived using an analysis algorithm.