Skip to main content

Glossary

Definitions of terms and concepts used in Grand Central documentation.

A

API Gateway
Entry point for all API requests, handling routing, authentication, and rate limiting
Availability Zone
Isolated location within a region for high availability

C

Circuit Breaker
Design pattern that prevents cascading failures by stopping requests to failing services
Connector
Pre-built integration that connects Grand Central to external systems
CQRS
Command Query Responsibility Segregation - pattern separating read and write operations

D

Distributed Tracing
Method for tracking requests across multiple services

E

Event Sourcing
Pattern where state changes are stored as a sequence of events

H

Health Check
Endpoint that reports the health status of a service
Horizontal Scaling
Adding more instances of a service to handle increased load

I

Idempotency
Property where an operation produces the same result when executed multiple times

L

Load Balancer
Distributes incoming traffic across multiple service instances

M

Microservices
Architectural style where applications are composed of small, independent services

O

Observability
Ability to understand system behavior through logs, metrics, and traces

R

Rate Limiting
Controlling the number of requests a client can make in a time period
Retry Logic
Automatically retrying failed operations with backoff strategies

S

Service Mesh
Infrastructure layer that handles service-to-service communication
SLO (Service Level Objective)
Target level of service reliability

T

Throughput
Number of requests processed per unit of time

V

Vertical Scaling
Increasing resources (CPU, memory) of existing instances

Need More Definitions?

If you don’t find a term here, check the relevant section documentation or contact support.