Last week the first part of the ‘Build, connect and extend to the cloud with
Citrix Workspace Cloud’ blog was published. You can find it here. Make sure you have read it before continuing this blog post.
Now it’s time to dig into some details.
CWC from a technical perspective
A traditional Citrix environment has several Citrix related core components within the IT infrastructure. So, besides the workloads, functionality to employees, we have a XenDesktop/XenApp controller, Licensing server, XenMobile Server, ShareFile StorageZone Controller, StoreFront servers, NetScaler and of course a SQL instance, at least for your XenApp/XenDesktop site configuration.
Let’s take a XenApp/XenDesktop environment as an example. An on-premises environment has all these different components installed, which you have to maintain. With CWC most of the core components are delivered “as a service”. The Delivery Controller, Licensing, StoreFront, and SQL are brought to you as a service. The images below illustrate the difference between a traditional on-premises and a CWC environment. The CWC components are ‘in the cloud’.
This is an example for a XenApp/XenDesktop environment. As you can imagine the XenMobile Server (appliance) and the ShareFile Control Plane are deployed into CWC as well.