To survive in the next five years, companies will need to understand, embrace, and implement enterprise web 2.0 technologies and solutions. Today, employees, partners and customers expect more access to information and in an easy to use/ customizable format. Companies need to consider what they do today to meet the needs of today and set the foundation for the future.
If you step outside the vendor’s skin, you realize that enterprise customers need help determining what the most important applications are how to prioritize implementations. To do this, it is important to understand that there are three categories of enterprise applications. Although this may seem like a simplification, it provides a framework that companies can use to prioritize.
Enterprise applications fall into three categories:
- Persistent Applications
- Continuous Web Applications
- Synthesized Applications
Persistent Applications
After working with multiple large and medium sized clients, it was clear that certain applications do not need to be changed. Many of these applications consist of a fat client, so users can do most of the work locally and a server component for storage. In the past, vendors have used the term legacy applications to describe this category. The term “legacy” is no longer relevant. Legacy means that it is old. Many applications in this category are old and new. Would you call Microsoft’s Publisher a legacy application? No, but it is a persistent application in that, you may never change it. Further, persistent applications are ones where a customer has made a decision to leave it unchanged.
For instance, one large customer had a brand new CAD application. The users never accessed the application outside of work and they would never consider logging in after hours. This company wanted to switch to a web application or create services from the legacy. After researching alternative options, they decided to leave this application alone.
Note: Microsoft’s Outlook and Office may be considered the largest/ most used Persistent Applications. Many companies may argue that other office and web mail companies are gaining market share. However, the reality is that for now, Microsoft owns this space.
Continuous Web Applications
As easy as Persistent Applications are to understand, Continuous web applications and synthesized applications are very hard to understand. Just to make things more confusing, synthesized or SOA enabled applications can and usually are delivered as web applications. So why do we need a distinction between the two? The answer is simple and straight-forward, Continuous web applications are like monolithic and persistent application, only web apps are delivered over the web and through a browser.
Web applications can be hosted on premise or by the application provider. When the application is hosted and managed by the application provider it is called Software as a Service (SaaS). In the minds of many vendors, the SaaS model is very different from the old Application Service Provider ASP model that failed as the bubble burst. How the ASP model and SaaS model differ is for the vendors to explain.
Note: Continuous web applications can be delivered solely within the enterprise. For instance many of the new wikis are just web applications.
Another interesting side note: I recently spoke with a wiki provider who would not let their employees work remotely and a remote access company that needed all their employees in one location. These are the companies we rely on to drive enterprise web 2.0. Whether wikis will survive in the long term or be replaced by Synthesized Applications such as SOA, BPM and Mash-ups, remains to be seen.
Synthesized Applications
SOA is still confusing to many customers, users, business people and even many vendors. Now, let me make even more confusing and then simple. SOA applications can be delivered as web applications. In fact, most SOA enabled applications are based on web applications.
The major characteristic of this category is – using multiple inputs to create a single application. These inputs can be many things including but not limited to services, processes, data structures, data, other applications,
So why choose “synthesized”? Many vendors, customers and analysts use the term composite applications. However, because of the over use of the term and the association with SOA applications it is important to create another category.
Synthesized applications are much more than SOA. Synthesized applications include enterprise application integration (EAI), business process management (BPM), Enterprise Service Bus (ESB), Service oriented architecture (SOA), and mash-ups. Yes, mash-ups.
Note: “Synthesized Applications” is the only category that provides a foundation for companies to build a complete enterprise web 2.0 strategy.
Application Framework
For many organizations, new technologies are those that were introduced three of four years ago. For example, I spoke with a technology vendor that was implementing WLAN access to its executives. That’s right, the executives…the next step was to certain employees and then, maybe, across the enterprise. Can we expect customers and clients to embrace new technologies when vendors are struggling to stay ahead of the latest?
The short answer is – yes. Customers will embrace new ideas and technologies by creating a solid framework, building a foundation and managing changes. As part of the overall “Enterprise Web 2.0 for the CIO” series, this blog provided the framework for companies understand and analyze how new applications will be built and/or bought and how legacy applications will be delivered.
Time to vote on the next blog:
- More on Enterprise Web 2.0 Applications
- Next area of Enterprise Web 2.0 – Connectivity