Glossary

A snapshot of the state of your clusters at a given point in time.

A fully-managed TigerGraph instance or a group of instances connected together. TigerGraph allows High Availability (HA) clusters that provide redundancy so that user instances are not interrupted in the case of a server outage.

Information authenticating a user’s identity. TigerGraph allows either username:password or API token credentials.

TigerGraph’s visual interface for designing a graph, ingesting data, exploring the graph, developing and running queries, and visualizing the results.

TigerGraph’s query language for fast and scalable graph operations and analytics.

One virtual machine or virtual server.

An internal TigerGraph characteristic of a TigerGraph cluster that determines how the data in the database will be distributed

A characteristic of the cluster design that will determine the number of copies of data that will be stored in the cluster.

Allocating more or fewer resources to existing instances, enabling a balance between cost and performance as workloads change.

A REST server customized for TigerGraph users.

A policy-neutral access-control mechanism defined around roles and privileges.

A formal description of a graph’s data model.

The previous name for a cluster, or a fully-managed TigerGraph deployment.

A database user with its own roles and privileges for different graphs stored on a cluster.

A virtual central processing unit. A vCPU is a core within a virtual machine inside TigerGraph Cloud.

Virtual Private Cloud. A private cloud environment inside a public cloud. By default, your instances are separated from other TigerGraph users by different VPCs. The term "VPC" is used by AWS and GCP, while Azure uses "VN" for "Virtual Network."

A network between two VPCs allowing instances to communicate as if they are on the same network.

A browser-accessible command line for running GSQL commands on a TigerGraph Cloud cluster.