A year in the cloud
For cloud enablement of GridGain and Apache Ignite tools and services, 2021 has been a busy year. Mid-year we launched a SaaS version of GridGain Control Center—for customers who need easy access to troubleshooting and monitoring tools for their Ignite and GridGain clusters. Building on our initial SaaS offering, we have now added a self-service version of GridGain Nebula.
What is GridGain Nebula?
GridGain Nebula SaaS is a managed service for GridGain and Apache Ignite. The service streamlines cluster provisioning in public clouds, standardizes cluster configurations and security, and maintains SLA uptimes with the backing of a 24x7 operations team. Nebula clusters are created within a dedicated infrastructure to ensure isolation and resource availability. The service uses pay-as-you-go billing so that customers are charged only for what they use and can cancel at any time.
The process of setting up a cluster begins with a few basic decisions, such as about the cloud data center where the cluster will reside, the node resource capacity, and the cluster size. Cluster configurations are based on best practice standards so that the cluster is configured properly from the get-go.
Optional configuration settings, such as storage data region allocation, enable developers to decide whether the cluster nodes should be persistent, in memory, or a combination of persistent and in memory. Security access lists, SSL, and authentication are also configurable.
As the Nebula cluster is provisioning and after it is running, applications can be connected through a wide variety of client APIs and languages. JDBC, Java thin client, Java thick client, Python, REST, .NET, and more can be used to connect the application to the cluster. Connection templates provide sample snippets that can be tailored to the application code.
Maintenance and support
Currently, Nebula clusters have a 99.0% uptime SLA and include automated, daily backups of cluster data. The Nebula 24x7 team actively monitors cluster health and is responsible for maintenance, restarts, and recovery—as needed to maintain SLAs. To eliminate downtime, cluster version upgrades are performed in a rolling fashion.
GridGain Nebula uses Control Center management and monitoring tools out of the box, so dashboards can be set up to monitor key application performance metrics and to develop and fine-tune SQL queries.
If an application requires custom libraries (for Ignite compute tasks, services, or any other reason), the Deployments tab can be used to manage the life cycle of the libraries and their dependencies. Through multiple secure protocols, deployments can pull from a Maven repository or from a direct resource link. After configuration is complete, the libraries are deployed to each node of the cluster. They can then be versioned, cloned, deployed, and decommissioned.
Here are some useful links to get started with GridGain Nebula: