Search docs.molo17.com
    A newer version of this documentation is available.
    View Latest (v2.3)

    System Requirements

    Before deploying Gluesync, ensure your environment meets these requirements for optimal performance.

    Prerequisites Checklist

    Containerized Deployment Setup

    Gluesync is designed to run efficiently in containerized environments. We recommend using Docker or Kubernetes for deployment, depending on your needs and familiarity.

    Docker Setup

    Requirement Details

    Docker Engine & Docker Compose

    Ensure Docker Engine and Docker Compose are installed on your system. These are required to run the Gluesync Docker Compose kit.

    Installation Guides

    * Docker install guide (Windows, macOS, Linux) * Windows Server users: Use Docker Engine binaries for production-grade setup

    Gluesync Docker Compose Kit

    After installation, follow the Gluesync documentation for using the Docker Compose kit you received via email. See Useful Links below.

    Note

    Gluesync documentation does not cover Docker installation. For step-by-step instructions, refer to the official Docker documentation or community tutorials.

    Cannot access Docker Hub due to security constraints?

    There are two ways for working around this: allow (whitelist) Docker registry at your proxy/firewall level, specifically allowing the following trusted domains: *.docker.io, *.docker.com, *.dckr.io

    Otherwise, you can save the images via docker image XYZ save > image.tar and load them on either your private registry (if any) or in the machine where docker is installed (it will load them in its own local registry) via docker image load < image.tar

    Kubernetes Setup

    Requirement Details

    Kubernetes Cluster

    A running Kubernetes cluster (e.g., Minikube for testing, or a production-grade cluster for deployment). LTS Linux is recommended for production.

    kubectl CLI

    Install and configure kubectl to interact with your cluster.

    Supported Distributions

    Kubernetes (recommended), OpenShift, or an equivalent orchestrator. See production specs above for hardware guidance.

    Installation Guides

    * Kubernetes install guide * kubectl install guide

    Gluesync Kubernetes Deployment

    Refer to Gluesync documentation or contact support for deployment guides specific to Kubernetes environments.

    Note

    Gluesync documentation does not cover Kubernetes installation. For setup help, refer to the official Kubernetes documentation.

    Source Database Requirements

    Requirement Details

    Connection Details

    * Username and password * Connection string (IP address/port) * Table names * TLS certificates (if secure authentication required)

    Access Permissions

    Database user must have appropriate read permissions

    Target System Requirements

    Requirement Details

    Connection Details

    * Destination (bucket or database) * Connection string (IP address/port) * Username and password * TLS certificates (if secure authentication required)

    Access Permissions

    Write permissions to target location

    We recommend using a database management tool for easier setup and testing. Our QA team regularly uses:

    Note: These are suggestions only - use any database tool you’re comfortable with.

    Environment Specifications

    POC / Demo Environment

    Component Requirement

    Operating System

    Windows, macOS, or Linux

    Container Platform

    Docker, Docker Compose, or Kubernetes

    Hardware

    * 8 GB RAM (minimum) * 8 vCPU * 10 GB free disk space (Additional space needed for Prometheus monitoring)

    Production Environment

    Recommended specs for handling ~35,000 rows per second (RPS)

    Component Requirement

    Operating System

    Linux (LTS version recommended)

    Container Platform

    Kubernetes (recommended), OpenShift, or equivalent orchestrator

    Cluster Configuration

    3 Kubernetes nodes for High Availability (HA)

    Total Hardware Resources

    * 32 GB RAM * 16 vCPU * 100 GB free disk space (Additional space needed for Prometheus monitoring)

    These specifications are baseline recommendations. Actual requirements may vary based on:

    • Data volume

    • Number of concurrent connections

    • Complexity of transformations

    • Monitoring requirements