Thin Clients in The Dark and Distant Past
The IT world loves to swing back and forth between moving processing out to the user via fat clients and moving processing back to the server, leaving users with thin clients.
The battle is a long running one that started with the first appearance of multi-user computer systems several decades ago and has continued to this day. And it will likely continue for a very long time to come.
When I began working in IT, thin clients were simple text terminals attached to a single, central server via serial connections. Limited to very basic text input, these served their purpose at the time by providing relatively low cost computing to a large number of users. The system wasn't pretty or glamorous, but it was quite functional.
Eventually centralized power was available in such quantities and at such a low price point that graphical applications could be run with almost as much responsiveness from the server. Clients could be "thin," needing just a shim of an operating system - enough to provide remote access back to the server.
Thin computing became the darling of the industry again and the term itself arose. Centralized processing again moving towards the vogue.
Why IT Managers Love Thin Clients
Administrators love the central computing model because data and configuration remains in one place. Backups and management are a breeze. The idea, at least in theory, is that the thin client set-up makes desktop support becomes a non-issue all desktop clients are nothing more than commodity components, easily replaced. Since nothing is stored or configured on the thin client there is nothing to support there.
In the initial swings of the "thin computing pendulum," the market movement was dramatic. When text terminal computing first became available this was practically the only model used in the real world. The value was so dramatic that no one could really justify doing anything else.
Yet when the PC was introduced the movement to the fat client was so ubiquitous that many younger IT professionals today have never actually seen text terminals in use. This is true even though the move to fat "PC" clients was not as all encompassing as the move to text terminals had been one pendulum swing earlier.
The PC model was generally better for end users because it mimicked how they used computers at home. It also gave them more options for customization and, for better or worse, opportunity for them to begin installing software of their own rather than only software preconfigured for them on the central server.
Thin Clients And Fat Clients Grow Similar
Over time there have been a lot of developments from both camps, giving each more and more of the advantages of the other.
Central domain services such as Microsoft's Active Directory have come along, allowing central management to extend out to fat clients. This brings control and management more in line with traditional thin computing models.
Likewise, companies like Citrix have worked very hard developing new technologies that allows thin clients to perform much more like robust fat clients, making their use as seamless as possible for end users. Offline use is even possible for laptop users.
Most shops today have adopted hybrid models: Fat clients where they make sense, thin clients for certain categories of users and for remote workers and continuity of business scenarios.
Web Apps and the Browser as Thin Client
Over the past decade we have seen a shift in the way that business applications are created and deployed. Today almost all business applications are web-based and have no client platform dependency. This affords IT departments with a potential new opportunity - to shift from a traditional thin client platform - requiring remote graphical access - to the browser as the new thin client platform.
The move to web apps has happened slowly and most businesses have a rather large legacy codebase on which they are quite dependent. This cannot be easily transferred to the new web app architecture and some apps simply are not good candidates for this architecture.
But by and large the majority of new business applications are web based, written most often in Java or .NET, and these apps are prime candidates for a new thin computing model.
If our custom business apps are available via the browser, then our only commonly used apps that now holding us back are the traditional productivity apps our office suites widely used by nearly all staff.
Very few desktop apps are actually pervasive except for these. Increasingly we are seeing browser-based alternatives to the traditional office suites. Everyone is very aware of Google Apps as a pioneer in this area with Microsoft now offering online MS Office as well.
But the popular offerings making consumer news headlines require businesses to totally rethink long term strategies. This involves keeping critical business data within their walls and is not likely to be highly disruptive to the enterprise for quite some time.
What does pose a threat to the status quo is other alternative software products such as ThinkFree office, which is installed within the organization. It is used and secured internally just like any other normal business application.
This category of "traditionally installed internal web applications" will allow enterprise IT departments to begin to reconsider their end users' platforms without having to reevaluate their entire concept of IT in general. The biggest barriers to this today are lingering business applications and power users using specific desktop apps that cannot be encapsulated within a browser.
Mixing Thin Clients, Browsers, and Traditional Apps
One of the great advantages, however, of the browser as the new thin client is how simple it is to mix browser-based apps with traditional apps. The move is transparent and most large businesses are moving in this direction today - even if there is no overarching strategy to do so. The market momentum to develop all new apps for the web is causing this to happen naturally.
Another key advantage of a completely "web based" architectural model is the great ease with which it can be exposed for users outside of the corporate network. Instead of using cumbersome VPN clients and company laptops, employees can find any web browser, sign in to the company network and have secure business applications delivered to any browser, anywhere.
What all of these devices have in common is a focus upon being primarily thin web appliances - thin clients for consumers. With the majority of consumer computing focused upon web connectivity, the need for anything else from a platform is nearly non-existent in the consumer market. So within a very short period of time users who once expected their home PC experience to be duplicated in the office will see web-based thin computing as the standard.
When this shift happens IT departments with need to rethink their internal application delivery strategy. The change doesn't have to be dramatic if current development trends are used commonly and legacy systems are routinely updated. In fact, one of the great benefits of this new model is that traditional fat clients function very well as browser platforms and will do so for a very long time to come, most likely.
Companies adopting this model will likely be able to slow desktop purchasing cycles and prepare for purchasing some form of traditional thin client with embedded browser. Or theyll move to a business version of the new Nettop trend that we are beginning to see emerge in the consumer space.
Some businesses may even attempt the rather dangerous path of using consumer devices. But the lack of management and security features will likely keep this from being popular in all but rare instances.
Hybrid Thin Client Scenarios
I believe, though, that this swing of the pendulum will not be as dramatic as the last one, just as it was not as dramatic as the swing before that. It will be an important trend but IT departments understand more and more that no new technological shift is a silver bullet. With each new opportunity comes new challenges.
Most IT departments will need to implement some degree of browser-based thin computing over the next few years, but most will retain a majority user base of fat clients. Hybrid environments, like we've seen for many years with more traditional models, will continue as before. Each technology will be used in target areas where they make the most sense.
The one area where thin clients continue to be challenged the most is in mobile computing. Here, disconnected users end up being digitally marooned away from their company networks, unable to continue working until network connectivity is reestablished.
This is a significant issue for power users who must travel extensively and need to be able to continue working regardless of their current connectivity. Today this is being solved in the traditional thin client arena thanks to companies like Citrix who continue to advance the state of the art in thin application delivery.
In the browser-based arena, in the past we have had to turn to technologies like Google Gears and Adobe AIR, but these had poor market penetration. Coming down the pike, however, is the new HTML 5 Offline API, which is set to redefine how the web works for users who need to go "off the grid" from time to time.
With HTML 5 incorporating offline capabilities and a richer feature set into the specification for the web itself, we expect to see broad and rapid adoption from all of the leading vendors - most likely even before the draft standard is finalized. While still quite some ways away this new standard will certainly lay the groundwork for a significant shift towards the browser as a ubiquitous, standard and robust platform.
The future of thin computing looks to be incredibly promising, both in the enterprise as well as for the first time in the consumer arena. Adoption of thin computing models will be spurred on by the current movement towards Software as a Service models. And SaaS adoption will continue to be encouraged by the widespread presence of thin computing devices.
In many ways browser-based thin computing represents the technology aspect that is now maturing in the SaaS arena, where SaaS itself is maturing in social acceptance rather than technical feasibility.