Skip to content
Connect2id

Scaling and high-availability

Engineered for 24/7/365 uptime

Identity and token services are critical to many relying applications. The Connect2id server employs several strategies to ensure continuous availability:

  • Avoiding single points of failure: The web service layer and the underlying database can be clustered for high-availability (HA).

  • UI isolation: The front-end is decoupled from the Connect2id server as a separate application, allowing independent updates and scaling.

  • Live metrics: Over a hundred metrics are available for monitoring your Connect2id server cluster via a secure web API or streaming through Graphite or Prometheus.

  • Seamless scaling: Server nodes can be dynamically and transparently added or removed from the cluster.

  • Rolling upgrades: The server supports zero-downtime upgrades to ensure uninterrupted service.

Scaling and performance

We recommend deploying at least two Connect2id server nodes in a “stateless” or “replication” cluster mode to ensure high availability for your OpenID Connect and OAuth 2.0 services.

Small organisations, with users in the order of tens of thousand of users, can run a Connect2id server on a host with as little as 1 CPU and 2 GB RAM.

Large user bases can benefit from a Connect2id cluster where the handling of requests is balanced over multiple nodes. A single node on a typical 1-core CPU can handle between 100 and 300 logins per second. Nodes can be added or removed dynamically based on demand.

In-memory storage and caching of data such as sessions and client registrations reduces latency and load on your backend database.

Supported databases

A cluster of Connect2id servers can be deployed on your premises or in a cloud provider of your choice.

Supported backend databases include MySQL, PostgreSQL, SQL Server, Oracle and DynamoDB. Redis can be used as an alternative in-memory and cache store to Infinispan.