Abstract: In an example embodiment, a workflow engine is introduced within a cloud landscape. Runbooks re then implemented as workflow templates within the workflow engine. The workflow engine allows for creation of workflows from the workflow templates as well as composing workflows from individual steps. The workflow engine provides a mechanism to describe workflow templates and workflow sets as code.

Abstract: Systems and methods include creation of a first instance of a tenant object in a database instance, association of the first instance of the tenant object with a first plurality of database artifacts including first data associated with the first instance of the tenant object, creation of a second instance of the tenant object in the database instance, association of the second instance of the tenant object with a second plurality of database artifacts including second data associated with the second instance of the tenant object, and reception and response to queries on the first data associated with the first instance of the tenant object and to queries on the second data associated with the second instance of the tenant object.

Abstract: In an example embodiment, a solution is provided that causes a binary used by an in-memory database application to be deployed in a separate container. The container with the binary may be called a “sidecar” to the container with the in-memory database application. Both containers mount the same path in the hosts shared filesystem to expose the binary to the application. There is no permanent connection between the two containers, and thus the binary can be updated individually without inducing a downtime of the in-memory database application.

Abstract: A data structure called a product version map is introduced. The product version map contains a catalog of available application versions to be used by the application orchestration services. It can describe the available versions. For each version, there is an image, such as a Docker® container image, that can be used to instantiate the application instance. Furthermore, in some example embodiments, an expiration date can be given, which could be used to enforce upgrades of application instances when their used version expires.

Abstract: Various examples are directed to systems and methods for monitoring a plurality of container-implemented software application instances. A first ping agent executing in an orchestration container may launch a worker process in the orchestration container. The worker process may launch first and second worker threads in the orchestration container. The first worker thread may send a first ping message to a first application instance executing in a first application container outside the orchestration cluster. The second worker thread may send a second ping message to a second application instance executing in a second application container outside the orchestration cluster.

Abstract: Disclosed herein are system, method, and computer program product embodiments for disaster resilience of applications managed by Kubernetes operators. An embodiment operates by creating an orchestration and worker cluster, where the worker cluster is coupled to the orchestration cluster by a proxy server. Custom resources are deployed to the orchestration cluster and custom resource controllers are deployed to the worker cluster. The proxy server federates these custom resources between the orchestration cluster and the worker cluster. During disasters, the worker cluster is recreated and reconciled to prevent loss of the federated cluster.

Abstract: A data structure called a product version map is introduced. The product version map contains a catalog of available application versions to be used by the application orchestration services. It can describe the available versions. For each version, there is an image, such as a Docker® container image, that can be used to instantiate the application instance. Furthermore, in some example embodiments, an expiration date can be given, which could be used to enforce upgrades of application instances when their used version expires.

Abstract: In an example embodiment, a workflow engine is introduced within a cloud landscape. Runbooks re then implemented as workflow templates within the workflow engine. The workflow engine allows for creation of workflows from the workflow templates as well as composing workflows from individual steps. The workflow engine provides a mechanism to describe workflow templates and workflow sets as code.

Abstract: A method for managing the configuration of an in-memory database running in a cluster of computing nodes may include receiving a configuration request to apply, to an instance of an in-memory database running on a cluster of computing nodes, one or more temporary changes to a configuration of the in-memory database. In response to the configuration request, an indication to deprecate the configuration profile may be added to a configuration profile associated with the instance of the in-memory database. The configuration profile may be deprecated based at least on the configuration profile being associated with the indication. The deprecating including restoring, to a state prior to the application of the one or more temporary changes, the configuration of the in-memory database. Related systems and articles of manufacture, including computer program products, are also provided.

Abstract: A method for managing the configuration of an in-memory database running in a cluster of computing nodes may include receiving a configuration request to configure an instance of the in-memory database. The configuration request may include an identifier of a configuration profile specifying a value for each of one or more parameters of the in-memory database. The presence of the instance of the in-memory database and the configuration profile specified in the configuration request may be verified. Upon verifying the presence of the in-memory database and the configuration profile, the instance of the in-memory database may be configured based the configuration profile. The configuring may include setting, to the value specified in the configuration profile, the one or more parameters of the in-memory database. Related systems and articles of manufacture, including computer program products, are also provided.

Abstract: A data structure called a product version map is introduced. The product version map contains a catalog of available application versions to be used by the application orchestration services. It can describe the available versions. For each version, there is an image, such as a Docker® container image, that can be used to instantiate the application instance. Furthermore, in some example embodiments, an expiration date can be given, which could be used to enforce upgrades of application instances when their used version expires.

Abstract: In an example embodiment, a solution is provided that causes a binary used by an in-memory database application to be deployed in a separate container. The container with the binary may be called a “sidecar” to the container with the in-memory database application. Both containers mount the same path in the hosts shared filesystem to expose the binary to the application. There is no permanent connection between the two containers, and thus the binary can be updated individually without inducing a downtime of the in-memory database application.

Abstract: Disclosed herein are system, method, and computer program product embodiments for disaster resilience of applications managed by Kubernetes operators. An embodiment operates by creating an orchestration and worker cluster, where the worker cluster is coupled to the orchestration cluster by a proxy server. Custom resources are deployed to the orchestration cluster and custom resource controllers are deployed to the worker cluster. The proxy server federates these custom resources between the orchestration cluster and the worker cluster. During disasters, the worker cluster is recreated and reconciled to prevent loss of the federated cluster.

Abstract: A data structure called a product version map is introduced. The product version map contains a catalog of available application versions to be used by the application orchestration services. It can describe the available versions. For each version, there is an image, such as a Docker® container image, that can be used to instantiate the application instance. Furthermore, in some example embodiments, an expiration date can be given, which could be used to enforce upgrades of application instances when their used version expires.

Abstract: In an example embodiment, a solution is provided that causes a binary used by an in-memory database application to be deployed in a separate container. The container with the binary may be called a “sidecar” to the container with the in-memory database application. Both containers mount the same path in the hosts shared filesystem to expose the binary to the application. There is no permanent connection between the two containers, and thus the binary can be updated individually without inducing a downtime of the in-memory database application.

Abstract: A method for managing the configuration of an in-memory database running in a cluster of computing nodes may include receiving a configuration request to apply, to an instance of an in-memory database running on a cluster of computing nodes, one or more temporary changes to a configuration of the in-memory database. In response to the configuration request, an indication to deprecate the configuration profile may be added to a configuration profile associated with the instance of the in-memory database. The configuration profile may be deprecated based at least on the configuration profile being associated with the indication. The deprecating including restoring, to a state prior to the application of the one or more temporary changes, the configuration of the in-memory database. Related systems and articles of manufacture, including computer program products, are also provided.

Abstract: A method for managing the configuration of an in-memory database running in a cluster of computing nodes may include receiving a configuration request to configure an instance of the in-memory database. The configuration request may include an identifier of a configuration profile specifying a value for each of one or more parameters of the in-memory database. The presence of the instance of the in-memory database and the configuration profile specified in the configuration request may be verified. Upon verifying the presence of the in-memory database and the configuration profile, the instance of the in-memory database may be configured based the configuration profile. The configuring may include setting, to the value specified in the configuration profile, the one or more parameters of the in-memory database. Related systems and articles of manufacture, including computer program products, are also provided.

Abstract: In an example embodiment, a solution is provided that causes a binary used by an in-memory database application to be deployed in a separate container. The container with the binary may be called a “sidecar” to the container with the in-memory database application. Both containers mount the same path in the hosts shared filesystem to expose the binary to the application. There is no permanent connection between the two containers, and thus the binary can be updated individually without inducing a downtime of the in-memory database application.