Easy to Use and Extensible
Simple to Deploy and Manage
Ease of use is a top priority for ScaleOut Software, and ScaleOut SessionServer was designed to be as easy to manage as possible. It takes only a few minutes to install on each server within a farm, and all servers automatically form a common membership and transparently distribute the workload. You also can deploy ScaleOut SessionServer in public clouds, including Amazon EC2 and Microsoft Azure, using the step-by-step deployment wizard within ScaleOut SessionServer’s GUI management console.
Because of its symmetric, peer-to-peer design, ScaleOut SessionServer has no configuration store to create, manage, or potentially fail. The centralized GUI management console lets system administrators easily manage grid servers, track key performance parameters, and identify issues. A command-line control program also enables scripting of management procedures. ScaleOut SessionServer logs significant events to the Windows Event Log and includes a comprehensive set of Windows Performance Monitor counters.
Screenshot of the WIndows Management Console
To handle varying workloads, ScaleOut Session Server’s “elastic” in-memory data grid makes it easy to add more servers as the workload increases and then remove them to conserve resources when not needed. This is especially useful in public clouds where servers can be added on demand.
Flexible Deployment Models
ScaleOut SessionServer can be deployed directly on each web server in the server farm to form a distributed in-memory data grid (IMDG) spanning the farm. There’s no need to configure the IP load-balancer for server affinity since all sessions are accessible from any web server. Also, restarting ASP.NET’s worker process doesn’t affect client sessions because they are safely stored out-of-process in the IMDG.
ScaleOut SessionServer Hosted on a Web Server Farm
ScaleOut SessionServer also can be installed on a separate cluster of grid servers using the Remote Client Option. The use of a dedicated cluster hosting the IMDG is the preferred configuration because it offloads CPU, memory, and networking usage from the web servers, and it allows the IMDG cluster to be provisioned for best performance. It also allows the IMDG to be managed independently of the web server farm; restarting web servers does not affect the IMDG.
ScaleOut SessionServer Hosted on a Dedicated Server Farm
Extensible for Maximum Performance
Because session-state objects easily can grow to 100s of kilobytes or even megabytes in some applications, care has to be taken to avoid overloading the local area network (LAN), especially when accessing read/write pages on large web sites. This is an inherent consideration for any out-of-process session-state store.
However, ScaleOut SessionServer’s capabilities can be extended using ScaleOut StateServer’s APIs (licensed separately) to overcome this limitation and dramatically boost performance when handling web requests. Instead of holding each client’s complete session-state within a single object, the web application can store portions of the object within the IMDG as separate objects accessed by keys held within the session-state object. This reduces the size of the session-state object and speeds up access during web requests. It also reduces network and CPU overhead, enabling the web site to scale without overloading the LAN.