eBooks/eGuides

6 The requirements are your true north; if you like an option that doesn't meet some of the requirements, you have to determine if you can live without them until that gap is closed, if it ever is. As a service that you subscribe to, they have several interesting characteristics. First, you typically pay for the service per-user per-month, which makes the cost easy to calculate and track. The cost also comes from the OpEx budget, which is a benefit for some as they're forced to move to the cloud consumption model. You can sign long- term deals with these DaaS offerings that probably offer better pricing in turn for a longer commitment; if you subscribe, though, you have the option of exiting if your demand decreases or disappears. With the traditional license approach, organizations typically buy licensing and then pay for perpetual support. Given that it's a service, organizations can consume it on demand. All the design, deployment, and scaling aspects of the brokering layer are handled for you. Also, you're typically running the apps and desktops in the public cloud next to the DaaS offering, so you don't have to manage the infrastructure these are running on either, which in turn gets you out of monitoring and upgrading these layers. These DaaS offerings can potentially get your project off the ground faster and are less effort from the operational side. While the DaaS service covers the brokering and infrastructure layers, there remain operational tasks to perform. These duties include image building and updates, application installs and updates, user data, VPNs, and so on. Another benefit that cloud offers is the ability to potentially use data centers around the world to offer pools of applications or desktops near a group of users. This benefit doesn't always work out. For example, if the users have a tight reliance on data or a specific app in a datacenter that is far away, this ability is null.

• Cover