Next generation control plane architecture delivers better availability

We have separated our control and data planes. Control signals flow between the Workspot client and Workspot Control. Data flows directly between the Workspot client and the application, e.g., SAP,, etc. This separation between control and data planes is very critical for security, availability, and performance. The control plane is not in the critical path for most operations. Even if the cloud is unavailable, users can connect to their applications and desktops.



Workspot delivers faster & more reliable connections

Most end points are smart. Workspot is designed to take advantage of the end point whenever possible. Our cloud control plane pushes most of the information needed by a client to connect to an application or desktop onto the client itself. So the client can connect to a resource without even having to ask the cloud. This results in one click, direct connections to the resource. Faster. And more reliable. If there is a network connection available to the resource, the client will connect to the resource.

Workspot is infinitely scalable

Legacy VDI 1.0 solutions were built with traditional 3 tier architecture and can scale to thousands of users. The Workspot Cloud is built with micro-services that deliver infinite scalability. This is similar to how Facebook and Netflix are built. The Workspot Cloud is designed to scale to millions of users.



33 handshakes

VDI 1.0 has poor reliability & availability

In VDI 1.0, all the intelligence was built into the data center. The clients were “dumb”. They had to ask the data center for instructions on almost everything. This resulted in multiple round trips with tens of  handshakes for a user to get a simple connection to an application or a desktop.

A typical VDI 1.0 deployment contains multiple components deployed in highly available pairs — SQL Servers, Load Balancers, Portals, Brokers, Licensing Servers, Provisioning Servers, etc. Multiple components are involved in every single user request, sometimes multiple times. It takes 33 steps to fulfill a login request, as described by a Citrix engineer. Through the power of compounding, even if each of the steps are 99% reliable, the overall sequence is now only 71.77% reliable (0.99^33 = 0.7177). That’s only if everything works. If something does go wrong and a user is unable to login, how do you figure out which one of those 33 steps failed?

Discover Workspot’s built-in monitoring and analytics.

Reliability, availability and scalability