Abstract: Orchestration of data services in multiple cloud infrastructures using the same user interface. In an embodiment, a customer provisions a first data service on a first cloud infrastructure and then a second data service on a second cloud infrastructure, while using the same user interface. An orchestration server may receive a respective count of nodes (“universe”) desired for each data service and issue commands to the corresponding cloud infrastructure to cause the desired data service to be provisioned. Another aspect facilitates creation/provisioning of a data service spanning multiple cloud infrastructures. In an embodiment, an orchestration server receives as inputs, the set of cloud infrastructures and count of nodes (“universe”) desired for the data service, and thereafter issues commands to provisioning systems of the respective cloud infrastructures to cause the desired data service to be created/provisioned.

Abstract: An aspect of the present disclosure facilitates selection of leader nodes in distributed data services. In one embodiment, a distributed data service is provided operative based on multiple nodes. Upon receiving from a user a selection of a set of nodes that are preferred as leader nodes, a node contained in the set of nodes is set as a leader node in the distributed data service in view of the selection by the user. Accordingly, a user is provided control over the selection of leader nodes in the distributed data service.

Abstract: Orchestration of data services in multiple cloud infrastructures using the same user interface. In an embodiment, a customer provisions a first data service on a first cloud infrastructure and then a second data service on a second cloud infrastructure, while using the same user interface. An orchestration server may receive a respective count of nodes (“universe”) desired for each data service and issue commands to the corresponding cloud infrastructure to cause the desired data service to be provisioned. Another aspect facilitates creation/provisioning of a data service spanning multiple cloud infrastructures. In an embodiment, an orchestration server receives as inputs, the set of cloud infrastructures and count of nodes (“universe”) desired for the data service, and thereafter issues commands to provisioning systems of the respective cloud infrastructures to cause the desired data service to be created/provisioned.

Abstract: Orchestration of data services in multiple cloud infrastructures using the same user interface. In an embodiment, a customer provisions a first data service on a first cloud infrastructure and then a second data service on a second cloud infrastructure, while using the same user interface. An orchestration server may receive a respective count of nodes (“universe”) desired for each data service and issue commands to the corresponding cloud infrastructure to cause the desired data service to be provisioned. Another aspect facilitates creation/provisioning of a data service spanning multiple cloud infrastructures. In an embodiment, an orchestration server receives as inputs, the set of cloud infrastructures and count of nodes (“universe”) desired for the data service, and thereafter issues commands to provisioning systems of the respective cloud infrastructures to cause the desired data service to be created/provisioned.

Abstract: An aspect of the present disclosure facilitates selection of leader nodes in distributed data services. In one embodiment, a distributed data service is provided operative based on multiple nodes. Upon receiving from a user a selection of a set of nodes that are preferred as leader nodes, a node contained in the set of nodes is set as a leader node in the distributed data service in view of the selection by the user. Accordingly, a user is provided control over the selection of leader nodes in the distributed data service.

Abstract: An aspect of the present disclosure facilitates selection of leader nodes in distributed data services. In one embodiment, a distributed data service is provided operative based on multiple nodes. Upon receiving from a user a selection of a set of nodes that are preferred as leader nodes, a node contained in the set of nodes is set as a leader node in the distributed data service in view of the selection by the user. Accordingly, a user is provided control over the selection of leader nodes in the distributed data service.

Abstract: A storage device uses non-volatile memory devices for caching. The storage device operates in a mode referred to herein as write-back mode. In write-back mode, a storage device responds to a request to write data by persistently writing the data to a cache in a non-volatile memory device and acknowledges to the requestor that the data is written persistently in the storage device. The acknowledgement is sent without necessarily having written the data that was requested to be written to primary storage. Instead, the data is written to primary storage later.

Abstract: Orchestration of data services in multiple cloud infrastructures using the same user interface. In an embodiment, a customer provisions a first data service on a first cloud infrastructure and then a second data service on a second cloud infrastructure, while using the same user interface. An orchestration server may receive a respective count of nodes (“universe”) desired for each data service and issue commands to the corresponding cloud infrastructure to cause the desired data service to be provisioned. Another aspect facilitates creation/provisioning of a data service spanning multiple cloud infrastructures. In an embodiment, an orchestration server receives as inputs, the set of cloud infrastructures and count of nodes (“universe”) desired for the data service, and thereafter issues commands to provisioning systems of the respective cloud infrastructures to cause the desired data service to be created/ provisioned.

Abstract: An aspect of the present disclosure facilitates selection of leader nodes in distributed data services. In one embodiment, a distributed data service is provided operative based on multiple nodes. Upon receiving from a user a selection of a set of nodes that are preferred as leader nodes, a node contained in the set of nodes is set as a leader node in the distributed data service in view of the selection by the user. Accordingly, a user is provided control over the selection of leader nodes in the distributed data service.

Abstract: Techniques are provided for managing cached data objects in a mixed workload environment. In an embodiment, a database system receives request to access a target data object. The database system determines whether the request to access the target data object is associated with a first type of workload or a second type of workload. In response to determining that the request is associated with the first type of workload, the target data object replaces a least recently used data object in a cache. In response to determining that the request is associated with the second type of workload, the target data object is cached based on an associated access-level value.

Abstract: Techniques are provided for managing cached data objects in a mixed workload environment. In an embodiment, a database system receives request to access a target data object. The database system determines whether the request to access the target data object is associated with a first type of workload or a second type of workload. In response to determining that the request is associated with the first type of workload, the target data object replaces a least recently used data object in a cache. In response to determining that the request is associated with the second type of workload, the target data object is cached based on an associated access-level value.

Abstract: A storage device uses non-volatile memory devices for caching. The storage device operates in a mode referred to herein as write-back mode. In write-back mode, a storage device responds to a request to write data by persistently writing the data to a cache in a non-volatile memory device and acknowledges to the requestor that the data is written persistently in the storage device. The acknowledgement is sent without necessarily having written the data that was requested to be written to primary storage. Instead, the data is written to primary storage later.