Scaling and Sizing

This page provides guidance on scaling and sizing your ZigiOps deployment based on the expected amount of integration data flowing through your integrations.

Depending on the integration use case, data volume, and deployment scenario, ZigiOps supports two complementary scaling approaches:

• Vertical scaling

• Horizontal scaling

How Do You Choose the Right Deployment Size?

Deployment Types Overview

The table below provides recommendations on which deployment type to use, based on the average expected integration throughput. Use this table as a starting point when planning a new deployment or evaluating growth.

Deployment	Configuration Items	Events per Second	Metrics per Second	ITSM / DevOps Records per Second
Small	Up to 10,000	100	100	100
Enterprise	10,000 to 100,000	200	300	200

What Infrastructure Resources Are Required?

Infrastructure Requirements by Deployment Type

The table below provides recommendations for CPU, memory, and disk resources based on the selected deployment size. Actual requirements may vary depending on integration complexity, transformation logic, and workflow design.

Deployment	CPU	Memory	Disk
Small	Dual-Core Processor (2.8 GHz or more)	4 GB	10 GB
Enterprise	Quad-Core Processor (2.8 GHz or more)	8 GB	20 GB

Scaling Strategies in ZigiOps

ZigiOps supports two primary scaling strategies. These approaches can be used independently or combined, depending on growth patterns and architecture requirements.

Vertical Scaling

What Is Vertical Scaling?

Vertical scaling increases the capacity of a ZigiOps deployment by adding more resources to an existing server.

This can be achieved by:

• Increasing CPU cores

• Increasing memory (RAM)

• Increasing available disk space

When Should You Use Vertical Scaling?

Vertical scaling is suitable when:

• You are within the Small or Enterprise deployment range

• You want a quick capacity increase

• You prefer to avoid architectural changes

Horizontal Scaling

What Is Horizontal Scaling?

Horizontal scaling increases capacity by adding more ZigiOps instances and distributing the workload across multiple servers. This approach enables ZigiOps to handle significantly higher data volumes and parallel workloads.

Horizontal scaling is recommended when the actual data volume exceeds the Enterprise deployment thresholds.

General Recommendations

• Start with vertical scaling for predictable growth

• Move to horizontal scaling for high-volume or enterprise-wide integrations

• Combine both approaches when required

• Reassess sizing regularly as integration usage grows

Related Documentation

• System Requirements

• Installation on Linux

• Installation on Windows