Gluesync - Sizing & minimum system requirements

Supported container orchestrators

Gluesync is a cloud-native application that is shipped using docker containers. This enables maximum flexibility in terms of where you can run the application both in terms of hardware and operating system.

Currently supported and tested environments where you can run Gluesync are listed below:

Container orchestrator Version

Kubernetes vanilla distribution, from v 1.24

Kubernetes Amazon EKS

Kubernetes Google GKE

Kubernetes Azure AKS

Kubernetes Fury distribution

Rancher 2.6.X
Docker Version

Docker from version 19.X

Docker-compose from version 1.28

Docker under Amazon ECS

Docker under Google Cloud
Podman Version

Podman from version 4.0

Podman Compose from version 1.0

Podman on Linux distributions (RHEL, Ubuntu, Debian, etc.)

Podman on Windows (via WSL2)

Gluesync can also run on bare metal environments as well as virtual machines, here we are collecting a list of environments where customers have successfully run Gluesync:

Environment (O/S, …​) Version

Red Hat Linux, requires Java SDK

Ubuntu Linux, requires Java SDK

Debian Linux, requires Java SDK

Docker under Google Cloud
Whilst Gluesync is officially shipped, as said, in containers there are cases where due to legacy implications they cannot be run. Our professional services team has made available some scripts to run Gluesync as a compatible system service for Linux and by request, Windows OS can be covered as well.

Minimum system requirements

  • a containerized environment is suggested (docker / docker-compose / K8s / OpenShift, …​);

  • 4 vCPU and 4GB of RAM;

  • 1 GB free disk space, used for logging redaction.

RAM is calculated on a given minimum of 32MB of required RAM amount for each table involved in a replication task.

Sizing your environment for Gluesync

Sizing is a process that involves our professional services in the first person. To properly size the infrastructure needed for running Gluesync for your specific use case we will require you to submit to your MOLO17 representative the following details:

  • Source & destination database type, version, patch version

  • Source & destination database hardware/infrastructure where it is currently running or where it is planned to run into:

    • RAM

    • CPUs

    • Disks (IOPS)

    • Networks and bandwidth

  • Use case description

    • Replication type:

      • local-to-local replication

      • Local-to-remote site replication

      • remote-to-remote replication

    • Number of tables/records involved

    • Number of mutations per seconds occurring on source database tables/collections that will need to pass through Gluesync

Once we have successfully collected all of that required information we will be able to fulfill your sizing scenario and follow up with a proposal to you.