GridGain Cloud Documentation

The GridGain Cloud Developer Hub

Welcome to the GridGain Cloud developer hub. You'll find comprehensive guides and documentation to help you start working with GridGain Cloud as quickly as possible, as well as support if you get stuck. Let's jump right in!

Get Started    

Getting Started

This page will help you get started with GridGain Cloud. You'll be up and running in a jiffy!

Overview

GridGain Cloud (Beta) is a distributed in-memory cache as a service. With GridGain Cloud you can start, load and use data in a GridGain cluster in the cloud in minutes. GridGain Cloud is fully compatible with GridGain Ultimate and Enterprise Editions 8.4.4 and later, and GridGain Professional Edition 2.4.4 and later. The service supports the following GridGain APIs:

Apache Ignite Support

Open Source users would be able to access their GridGain Cloud deployments with Apache Ignite distribution of version 2.5 and later.

Depending on the APIs you choose, GridGain Cloud can be used for the following use cases:

  • In-Memory Cache
  • Key-Value Store‚Äč

You can start a one node cluster for free. Larger clusters can be created for a small hourly fee - check the available plans at cluster creation time.

Sign-Up for GridGain Cloud

To use GridGain Cloud, simply sign-up for an account. Begin by opening the following hyperlink in your browser:

https://cloud.gridgain.com/

This will bring you to the following web page:

On the home page, you will see a Start FREE Trial button. Click this button and you will see the following sign up form:

Complete the form with the requested information and click the sign-up button at the bottom of the form.

You will receive an email confirmation and can then Sign in using the link on the home page.

Create Your First Cluster

After signing in, you can launch a free or paid cluster.

Free Cluster

Click the Free Cluster button to launch a free cluster. Note that you can launch only one free cluster at a time.

Paid Cluster

Click the Paid Cluster button to launch a paid cluster. A dialog box will appear that will prompt you to enter the amount of data you want to store and the number of redundant copies you want o maintain in your cluster.

Once you enter the values and click calculate, a pre-configured cluster form will appear. However, you can choose to provide your own configurations - such as the cluster name, cloud provider, region, choice of plan, and a password for the cluster- to suit your application needs. Once you have configured the options, click the Launch Cluster button.

The following example uses the defaults shown for the free tier:

The cluster is ready once the Status column shows Running.

Maximum number of clusters per user account

You can have up to 25 clusters running under a single user account. This limitation might be revisited in later versions.

Securing a Connection

GridGain Cloud enforces several data and connection protection approaches to ensure that the communication channel between the cloud and applications stays secured.

First, you need to set a hard-to-hack password for every cluster deployed on the cloud, as follows:

Second, GridGain Cloud generates a unique certificate for your account that has to be used to open a secured connection from applications side. It's required for all the available connectivity options such as JDBC/ODBC, REST or thin clients. To download the certificate, click on a name or a row of an already started cluster from the running clusters list

and download the required SSL certificate.

Refer to this documentation page for more details.

Connectivity and Usage

Once the cluster is started, you can connect to it from your applications. GridGain Cloud comes with a Demos section, located on the right of the screen, that explains how to start working with your deployment within minutes.

To get more details about the cluster and connectivity options, click on the cluster name or on its row from the clusters' list, to see a screen with the following information:

Note that the IP addresses for your connection strings will be different from the example shown.

The JDBC, ODBC, and REST connection strings allow you to connect your applications to the GridGain Cloud cluster from various programming environments. Further details about JDBC and ODBC are available from the relevant driver documentation pages.

Refer to the Connectivity Options page for further details about how to use the connection strings with your GridGain Cloud cluster.

Data Loading

Most production systems have large amounts of data that needs to be loaded into the cluster as soon as the cluster is up and running. This chapter describes data loading techniques such as streaming, COPY command and batch loading for clusters running on GridGain cloud.

Cluster Management and Monitoring

GridGain Cloud is integrated with GridGain Web Console that provides management and monitoring, as well as SQL query execution capabilities for GridGain and Apache Ignite clusters.

Clusters running on GridGain Cloud can be monitored and managed using the Monitoring functionality of GridGain Web Console. Click on the monitoring icon located in the menu on the left of the screen:

or select the Monitor option from the Actions drop-down menu.

You can now monitor and manage your cluster running on GridGain Cloud.

Refer to the Management and Monitoring page for further details about how to use the management and monitoring features with your GridGain Cloud cluster.

Resizing Your Cluster

You can add or remove nodes in a running cluster only. Note that this option is available only for paid clusters.

To resize your cluster, select the Resize option from the Actions drop-down menu.

Enter the desired number of nodes in the dialog window that appears.

The hourly price you pay for the cluster will be recalculated according to the new number of nodes.

Cluster Termination

To terminate a cluster, select the Terminate option from the Actions drop-down menu.:

Getting Started


This page will help you get started with GridGain Cloud. You'll be up and running in a jiffy!

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.