Installation Overview

The ScaleOut Active Caching service runs on top of a ScaleOut StateServer cluster, providing a web management UI. This service can be deployed behind a load balancer for high availability and scalability, or it can be run as a standalone service for simpler setups.

Deployment Topologies

After installing the ScaleOut Product Suite, the ScaleOut Active Caching service can be enabled on one or more nodes depending on the desired deployment topology. (See Windows Installation and Linux Installation for specific OS instructions.)

Local-Only Management

For simple deployments, the ScaleOut Active Caching service can be run as a standalone service on a single node. In this configuration, the ScaleOut Active Caching service only needs to be started on one host in your ScaleOut StateServer cluster. By default, the service uses a self-signed certificate and is only accessible locally through the ‘localhost’ DNS name. A SQLite database on the local filesystem can be used for storage.

If you want to access the service from multiple hosts in your cluster, it can be enabled on multiple nodes, but a PostgreSQL or Microsoft SQL Server database must be used for centralized storage.

local_ac_config

Load-Balanced Deployment

For deployment scenarios requiring high availability, scalability, and remote access, the ScaleOut Active Caching service can be run on multiple nodes behind a load balancer. In this configuration, the service must be started on each host participating in the deployment. A PostgreSQL or Microsoft SQL Server database must be used for centralized storage (SQLite is not supported for multi-node deployments). A DNS name should be assigned to the load balancer, and a trusted SSL certificate should be installed to secure communications.

remote_ac_config

See also