Your Big Data Partner
The Q.Trove design follows the guidelines used for other Q.Cloud services: The solution consists of an API and a component that executes commands in the background and sends them to the API. Like all Q.Cloud APIs, the Q.Trove API follows RESTful principles and can be operated via HTTP. The task manager – the executive component – is linked directly to the API and can see incoming API requests.
The Q.Trove-api service provides a RESTful API that supports JSON and XML to provision and manage Trove instances.
The Q.trove-taskmanager service does the heavy lifting as far as provisioning instances, managing the lifecycle of instances, and performing operations on the Database instance.
ORCHESTRATION & CLUSTERING
Integration with other Q.Cloud services, especially the orchestration solution Heat, is of great importance to Trove’s success. The Q.Cloud developers are aware of the need for Heat support and have already installed comprehensive Heat integration in Q.Cloud. This means, for example, that the resource type QC::Trove::Instance is available for native Heat templates; this resource type starts a DBaaS instance and provides it with the necessary credentials. Heat integration for Q.Trove provides everything needed for everyday life for clusters from multiple database nodes.
Q. TROVE GUESTAGENT
The guestagent is a service that runs within the guest instance, responsible for managing and performing operations on the Database itself. The Guest Agent listens for RPC messages through the message bus and performs the requested operation.