SecureAuth Deployment Sizing Recommendations
Depending on different needs, SecureAuth recommends choosing an appropriate sizing tier for your SecureAuth deployment on Kubernetes.
Tier 1
Designed for:
-
Single-region deployments
-
Up to 250 000 monthly active identities
-
Sustaining the load of 3 000 transactions per second.
| Component | Pods count | CPU per pod | Memory per pod |
|---|---|---|---|
| SecureAuth | 3 (one per AZ) | 2vCPU | 2 GB |
| Redis | 3 (one per AZ) | 2vCPU | 4 GB |
| CockroachDB | 3 (one per AZ) | 2vCPU | 8 GB |
Tier 2
Designed for:
-
Multi-region deployments (up to three regions)
-
Up to 1 000 000 monthly active identities in total across all regions
-
Sustaining the load of at least 6 000 transactions per second per region.
| Component | Pods count | CPU per pod | Memory per pod |
|---|---|---|---|
| SecureAuth | 3 (one per AZ) | 4vCPU | 4 GB |
| Redis | 3 (one per AZ) | 4vCPU | 8 GB |
| CockroachDB | 3 (one per AZ) | 2vCPU | 8 GB |
Tier 3
Designed for:
-
Multi-region deployments (up to 10 regions)
-
Up to 10 000 000 monthly active identities in total across all regions: Each region can handle 2000 000 monthly active identities independently.
-
Sustaining at least 10 000 transactions per second per region.
| Component | Pods count | CPU per pod | Memory per pod |
|---|---|---|---|
| SecureAuth | 3-5 (spread across AZs) | 6vCPU | 4 GB |
| Redis | 3-5 (spread across AZs) | 4vCPU | 16 GB |
| CockroachDB | 3-5 (spread across AZs) | 4vCPU | 8 GB |