Welcome!

@CloudExpo Authors: Yeshim Deniz, Dana Gardner, Pat Romanski, Liz McMillan, Elizabeth White

Related Topics: @CloudExpo, Containers Expo Blog

@CloudExpo: Article

The Future of Cloud Computing: Part 1 - VDI is DOA

The answer is not SaaS, nor VDI, nor Cloud; rather, an evolutionary compilation of all these technologies

The impact that Cloud Computing has brought to the IT industry to date has been primarily beneficial to application developers, system admins, and network architects, and not directly to end-users of technology.

Yes, IT developers and architects leverage cloud computing’s flexible and virtualized compute, storage, and network infrastructure to build resilient applications that eventually benefit end users due to improvements in speed-to-market and improved up-time statistics, but the direct benefits to the tech-needy end user are still rarely recognized.

Most daily users of personal and business class applications don’t have the turnkey, on-demand access to the applications they need. At work, their IT departments at work are too slow in delivering the apps they need or refuse to provide them due to cost, limited resources, or lack of recognized need. At home, users struggle to deploy software themselves due to complexity, time involved, or again, cost.

However, advances in cloud-powered software and service delivery have started to revolutionize the way that end-users (both business and consumer-level) think about acquiring the tools they need to succeed. These innovations will finally give end-users with their piece of cloud computing value and change the way software is delivered, licensed, and used both on-line and off-line. Over the next several weeks, I will be releasing several blog posts on the topic of the "Future of Cloud Computing".  Below is Part 1, which describes the unrealized promise and eventual demise of virtual desktops.

Innovations in streaming application code… rather than streaming pixels… will kill VDI before it even fully arrives.

Do users really like or want Virtual Desktops? From the start, the concept of virtual desktop infrastructure (VDI) is flawed for most real-world applications and use-cases.  No matter how optimized VDI compression companies claim their proprietary algorithms might be, they are still trying to push a proverbial “watermelon of pixels” though a relatively pinhole-size network to get what you need to your device.  It almost seems like all the stars have to align before VDI actually works for the every day, multi-location worker.

VDI technology refresher

Virtual Desktop Infrastructure (VDI) is a method of enabling end-users with a client device (PC, laptop, tablet, etc.) to access, log-in, and utilize a remotely hosted desktop environment.  In order for you to get access to and interact with the remote environment, compressed screen shots of the display (what you would see if you were standing in front of a monitor) of the VDI instance are streamed continuously via network connection to your client device’s display screen.  Meaning, that a user could have access to a completely different environment including OS, applications, and network without actually having that environment installed on their physical client device.

What’s so wrong with VDI now?

For the typical everyday business user, who works from a combination of office, home, client-site and car, using a virtual desktop sounds perfect, but in actual practice, it’s a real productivity killer due to several key flaws.

  • No offline access.  VDI requires a persistent high-speed internet connection throughout the entire session of usage on your virtual desktop… and while wifi is supposedly everywhere, it never seems to never be reliable, fast, nor secure… making accessing your applications and data “anywhere and anytime” more of an under-delivered promise than a reliable reality.
  • Not as "Green" as advertised.  For all its press about being “green”, VDI is actually incredibly wasteful because it is architected to leverage only the compute and storage of a hosted server or cloud environment, while completely ignoring the processing and storage power of your personal PC or tablet client-side device.  With the exception of true “thin-clients”, which are not widely used by consumer nor businesses to-date because of their inflexibility to be used for anything expect for VDI, your client device, whether it be a desktop or laptop PC, is still powered on and consuming a similar amount of power as it would if you were utilizing its local resources rather than just viewing the streamed screen shots of your VDI instance to your device’s display. Powerful client-side (e.g. PC, Mac) devices are so relatively cheap, yet are virtually (no pun intended) wasted when leveraging VDI.
  • Performance and Graphic degradation.  VDI struggles with graphic intense applications like Engineering, Drawing, CAD, GIS, and Gaming applications because most cannot use the device's local graphic card to render complex or fast-moving graphics locally rather than streaming non-3D and/or pixelated graphics from the VDI instance.
  • Cost.  A typical private VDI environment set up from a leading vendor is easily into the millions of dollars after accounting for new data center space, servers, networking, storage, and virtualization licensing.  A large price to pay to duplicate and even derogate some of the applications and services that your users are currently using.

How were we convinced streaming screenshots was "the right way" anyhow?

Undoubtedly there are benefits of VDI, but most of the benefits are to the IT staff, not end-users.  Most of these benefits to the IT staff surround topics of license management, patching, and security.  Although I understand these benefits, I don't know how IT shops got on the path of streaming pixels with VDI rather serving the code instead which would allow them to better optimize and control application delivery and licensing than what streaming screenshots could.

Using the server-side to deliver application functionality, data, and licensing on-demand to devices directly

Sending pieces of the code to your device, using your local device’s compute processing to run it, and then getting updates pushed from the mothership server whenever you connect or security requires it seems like a much more streamlined approach to a VDI-like environment than relying on a high-speed connection to stream pictures of screenshots from a remote data center slice of a server. In this scenario, IT admins still get all the manageability benefits and licensing controls for deploying applications on-demand that they get from VDI… all without spinning up an entire cloud infrastructure to host a VDI backend  and without wasting perfectly good client-side resources.

How to replace VDI... Streaming application code, not pixels

Benefits:
• Any software delivered to your own device
• VDI-like features still present- updates/patches pushed, zero-footprint device wiping
• Fast, reliable, offline-accessible local storage and processing (w/admin approval)
• Native graphics performance for CAD, GIS, Visualization, Gaming, etc.

The next step - making "Cloud-bursting" workloads a reality

Added Benefits:
• Application code, data, and compute are on local device & cloud for ultimate workload flexibility.
• Local & Cloud Storage Sync for redundancy and faster processing by chosen processing destination
• Local & Cloud Processing Capabilities – Cloud-bursting a workload becomes a reality
• Native Graphics Performance

More Advantages of streaming application code rather than pixels

  • Applications and data can live on both you local device and the cloud; enabling you to "cloud-burst" large jobs
    • Enables you to choose where you process your requests, choose the location, speed, and even cost of your processing jobs
  • More flexible and functionality-based licensing terms
    • Stream apps to first-responders in disaster response situations, then remote wipe once tasks complete
    • Sales teams can easily give customer's full trials with automatic licensing time-bombs
    • Create SaaS-like easy deployment without changing a single thing about your successful legacy desktop applications
  • Similar benefits to traditional VDI for application updates, bulk maintenance, and security
    • Admins are still administering one application package for everyone to use
    • Can auto-push critical security patches or application updates
  • Enables offline usage
    • Since the application code runs on the client device, with admin approval, user can take the application off-line indefinitely or, using time-bomb or usage-bomb licensing, admins can limit usage of the application for a certain period of time or for a specific task only.
  • Extends the life of Desktop applications
    • Traditional "boxed" software companies are spending millions of dollars and years of R&D time to re-engineer their software “for the cloud” because they think they only way to cloud-enable their software is to write from scratch a multi-tenant web application that recreates their technology’s traditional functionality.  However, the usual outcome of this new SaaS development is watered-down, bug-ridden functions compared to their flagship desktop product functions
  • Less risk of software piracy
    • Since only the application code for the functions you need is being streamed to you, your computer will never have full application code; making it much harder if not impossible to pirate, re-package, and re-sell and full pirated version of the software.
  • Superior application performance and 3D graphics rendering
    • When you stream code to the device instead of pixels,  it could remedy probably the biggest problem in VDI, application performance and graphics rendering.
    • This enables entire industries like CAD, Mapping (Geospatial, GIS), Gaming, and more to become usable and controllable, rather than becoming “IT silos” that get treated managed, updated, and secured differently than other non-graphic intense applications.

Although the technology to pull off this type of code-streaming environment might not be full baked yet, the groundwork for replacing pixel-streaming VDI has already been laid.  As the cost drops for cutting edge client devices and their amazing processing and graphics capabilities continue to wow customers and set expectations on user experience, VDI implementations will continue fail at achieving their once great promise to stream any application to every user via only a web connection. It seems that VDI is perhaps only a patch-over solution while we wait on something better to come about.  Code streaming to client devices may be that answer.

Watch for my upcoming post:
The Future of Cloud Computing - Part 2:  Why PaaS will fail and how Software-Stacks-as-a-Service (SSaaS) will replace it.

More Stories By Ryan Hughes

Ryan Hughes, blogging at www.RyHug.com, is the Co-founder and Chief Strategy Officer (CSO) of Skygone (www.skygoneinc.com), a Cloud Computing solution provider to SI's, ISV's, Commercial, and Government. Education: MBA in Project Management from Penn State University; BS in GIS from Bowling Green State University Ryan currently has 10 years in Enterprise-level IT Program Management and Operations Management, as well as vast experience in Enterprise System Design and Cloud implementation methodology.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


CloudEXPO Stories
The graph represents a network of 1,329 Twitter users whose recent tweets contained "#DevOps", or who were replied to or mentioned in those tweets, taken from a data set limited to a maximum of 18,000 tweets. The network was obtained from Twitter on Thursday, 10 January 2019 at 23:50 UTC. The tweets in the network were tweeted over the 7-hour, 6-minute period from Thursday, 10 January 2019 at 16:29 UTC to Thursday, 10 January 2019 at 23:36 UTC. Additional tweets that were mentioned in this data set were also collected from prior time periods. These tweets may expand the complete time period of the data.
The use of containers by developers -- and now increasingly IT operators -- has grown from infatuation to deep and abiding love. But as with any long-term affair, the honeymoon soon leads to needing to live well together ... and maybe even getting some relationship help along the way. And so it goes with container orchestration and automation solutions, which are rapidly emerging as the means to maintain the bliss between rapid container adoption and broad container use among multiple cloud hosts. This BriefingsDirect cloud services maturity discussion focuses on new ways to gain container orchestration, to better use serverless computing models, and employ inclusive management to keep the container love alive.
Artificial intelligence, machine learning, neural networks. We're in the midst of a wave of excitement around AI such as hasn't been seen for a few decades. But those previous periods of inflated expectations led to troughs of disappointment. This time is (mostly) different. Applications of AI such as predictive analytics are already decreasing costs and improving reliability of industrial machinery. Pattern recognition can equal or exceed the ability of human experts in some domains. It's developing into an increasingly commercially important technology area. (Although it's also easy to look at wins in specific domains and generalize to an overly-optimistic view of AI writ large.) In this session, Red Hat Technology Evangelist for Emerging Technology Gordon Haff will examine the AI landscape and identify those domains and approaches that have seen genuine advance and why. He'll also ...
Is advanced scheduling in Kubernetes achievable?Yes, however, how do you properly accommodate every real-life scenario that a Kubernetes user might encounter? How do you leverage advanced scheduling techniques to shape and describe each scenario in easy-to-use rules and configurations? In his session at @DevOpsSummit at 21st Cloud Expo, Oleg Chunikhin, CTO at Kublr, answered these questions and demonstrated techniques for implementing advanced scheduling. For example, using spot instances and cost-effective resources on AWS, coupled with the ability to deliver a minimum set of functionalities that cover the majority of needs – without configuration complexity.
The term "digital transformation" (DX) is being used by everyone for just about any company initiative that involves technology, the web, ecommerce, software, or even customer experience. While the term has certainly turned into a buzzword with a lot of hype, the transition to a more connected, digital world is real and comes with real challenges. In his opening keynote, Four Essentials To Become DX Hero Status Now, Jonathan Hoppe, Co-Founder and CTO of Total Uptime Technologies, shared that beyond the hype, digital transformation initiatives are infusing IT budgets with critical investment for technology. This is shifting the IT organization from a cost center/center of efficiency to one that is strategic for revenue growth. CIOs are working with the new reality of cloud, mobile-first, and digital initiatives across all areas of their businesses. What's more, top IT talent wants to w...