Evaluate Weigh the pros and cons of technologies, products and projects you are considering.

Retiring the Four-Platform Framework for Web services

Is the Four-Platform Framework outdated? ZapThink analysts believe so, and they propose a new framework for Web services implementation here.


Guest Commentary
Retiring the Four-Platform Framework for Web services
by Ronald Schmelzer and Jason Bloomberg, Senior Analysts, ZapThink, LLC

As an analyst firm, ZapThink sees many presentations from vendors and end users, and as a result we have seen a recurring vision for Web services that has outlived its questionable usefulness at representing how the market is implementing and producing products for real-world Web services and SOA solutions – namely Gartner's Four-Platform Framework of Web services. While the framework has helped many companies get started with their understanding of Web services, we believe it's time to move on. Fundamentally, the way in which the Four-Platform Framework is represented by vendors and end-users is inaccurate, incomplete, and in the final analysis, no longer helpful for either end-users or vendors as they struggle to grasp Web services or Service-Oriented Architectures (SOAs). In its place, ZapThink offers the SOA Implementation Framework, which we feel more accurately reflects the challenges companies face as they seek to implement SOAs, and the products vendors must produce to help their customers achieve the benefits that SOAs promise.

Explaining the Four-Platform Framework
The Four-Platform Framework contains a Web services producer platform, a Web services provider platform, a Web services consumer platform, and a Web services management platform. The producer platform consists of development tools and development approaches to exposing Web services interfaces on top of existing or green-field applications. The producer platform sits as the primary means by which developers create service interfaces and compose those services into higher-level business processes.

The provider platform is separate from the producer platform and is mainly responsible for hosting and provisioning Web services in the enterprise. The provider platform can contain application servers, middleware platforms, integration solutions, or even databases. In this vision, the provider platform supports the Web services architecture or SOA, which is essentially a best-practice architecture for implementing large enterprise systems.

According to the Four-Platform Framework, the consumer platform focuses on using and taking advantage of service interfaces provided by the producer and provider platforms. Finally, the management platform is a product solution or managed network that focuses on administrating and supervising the operation of running services to guarantee that they are meeting business needs.

So, according to this vision, an enterprise must implement each of these four platforms to deploy Web services and SOAs in the enterprise. While this certainly served an important role for people as they first tried to understand a new and emerging market, it is not an accurate, complete, or helpful representation of how end-users actually buy and implement Web services or SOAs in today's market.

The vision is inaccurate
The primary problem with the Four-Platform Framework is that it is simply not an accurate representation of the way that companies actually purchase and implement Web services. Simply put, the management, consumer, producer, and provider platforms are all inextricably linked together. Any Web services solution focused on solving integration problems – indeed, the only kind of Web services solutions most companies consider at this point in time – will have to consist of management, consumer, producer, and provider elements. Yet, companies never purchase these platforms separately. Rather, consuming, provisioning, and producing are all capabilities of the same platform (although a separate product does often provide management). A look at what IBM, Microsoft, CA, BEA, and others offer would confirm that there are not three or four separate Web services or SOA offerings from these vendors, but rather a single, unified solution that seeks to address the overall SOA challenge. If the platform vendors themselves aren't offering the Four-Platform Framework, then who is the Framework intended for?

Secondly, end-user companies don't evaluate Web services solutions as being composed of three or four parts, but rather as a single, cohesive solution set that addresses their immediate needs. RFPs from end users don't call for four separate platforms, but rather for a single Web services-based solution that solves their integration problems. Since the Four-Platform Framework doesn't reflect the way that vendors produce Web services products, or the way end-users purchase or implement them, it's clear that this vision is not an accurate portrayal of the current market.

The vision is incomplete
The Four-Platform Framework also doesn't include a number of important elements of the Web services and SOA markets. In particular, the framework does not include address the architectural components of an SOA. It is not clear where SOA tools, asset management suites, composite application solutions, and management tools that enable coarse granularity and loose coupling fit into the Four-Platform Framework. The framework also completely misses the role that UDDI plays and relegates it to keeping track of large numbers of services and aggregating services across organizations, rather than its central role as a service broker for enabling location independence.

In addition, the Four-Platform Framework is missing the critical role that security plays in implementing SOA solutions. Security platforms are not among the four platforms, nor are process or information integration platforms, for that matter. Finally, there is no allowance in the Four-Platform Framework of the role of emerging Enterprise Service Bus (ESB) products. Are these critical solutions part of the producer platform, the provider platform or neither?

The vision is unhelpful
Most importantly, a framework like the Four-Platform Framework must be helpful to both vendors and end-users. Unfortunately, the framework is not helpful to startups or emerging technology companies as it positions each of the four platforms as part of existing development tool, application server, or enterprise management markets. In this vision, there is simply no room for additional entrants. On the other hand, the vision is not even helpful for vendor market leaders, either. Most of the major platform vendors are attempting to sell well-integrated suites that reflect the realities of today's Web services market, and the Four-Platform Framework does little to support the major vendors as they attempt to sell unified solution suites that combine elements of the four platforms.

Finally, the vision is not helpful to end-users since it poorly reflects how the market for Web services products is truly evolving. Most importantly, the Four-Platform Framework is an example of what ZapThink calls a "horseless carriage" mentality. That is, the framework applies traditional ways of thinking about existing markets to new, emerging markets. In this case, the movement to SOAs demands new ways of developing, managing, deploying, and architecting IT assets. The word "platform," however, implies a runtime environment as part of an n-tier architecture, rather than loosely coupled applications composed into a services layer of abstraction. As a result, simply using the word "platform" in the Four-Platform Framework is fundamentally unhelpful.

The ZapThink Take: The SOA Implementation Framework
ZapThink eschews platforms altogether when discussing SOAs. Instead, our SOA Implementation Framework contains five parts: Service-Oriented Architecture tools, Service-Oriented Integration, Service-Oriented Process, Service-Oriented Management, and Web Services Security and Identity Management, as shown in the figure below. SOA tools include modeling, asset management, and service-oriented development tools that both IT and line-of-business need to build and maintain the services in the SOA, and maintain the abstraction layer that those services represent. Service-Oriented Integration provides runtime integration among disparate, heterogeneous systems integrating both at the application interface as well as at the information levels. Service-Oriented Process composes services into business processes that are themselves services, and provides the loose coupling to isolate the services that are produced from the processes that consume them. Service-Oriented Management enforces and enables loose coupling by guaranteeing the availability of services and providing visibility into their runtime operation, supporting the layer of abstraction that exposes system functionality in a loosely coupled manner. Finally, Web Services Security and Identity Management are fundamental prerequisites to building an SOA by providing the key capability of enterprise identity management that is required to maintain security context and policy enforcement across long-running service interactions.


Figure 1: The SOA Implementation Framework

ZapThink calls this vision a framework, because it offers pieces of the SOA puzzle that vendors and end-users must assemble. We use the word "implementation" because this framework applies both at design time and runtime – in fact, SOAs blur the distinction between the two, and thus, this vision is fundamentally a framework of the complete implementation lifecycle.

A final word
The technology is actually the easy part of moving to an SOA. The hard part, as with any situation that involves change, is the human part. End-users and vendors alike must actually change the way they think about the organization of their IT resources in order to make their SOAs successful. The Four-Platform Framework was useful in its time as people began to think about the power of Web services and SOAs, but that time is over. Today, people are beginning to think in service-oriented ways, and as such, they need a new framework for understanding the essential elements of a successful SOA.


Copyright 2003. Originally published by ZapThink LLC, reprinted with permission. ZapThink LLC provides quality, high-value, focused research, analysis, and insight on emerging technologies that will have a high impact on the way business will be run in the future. To register for a free e-mail subscription to ZapFlash, click here.

For more information:

  • Looking for free research? Browse our comprehensive White Papers section by topic, author or keyword.
  • Are you tired of technospeak? The Web services Advisor column uses plain talk and avoids the hype.
  • For insightful opinion and commentary from today's industry leaders, read our Guest Commentary columns.
  • Hey Codeheads! Start benefiting from these time-saving XML Developer Tips and .NET Developer Tips.

  • Visit our huge Best Web Links for Web services collection for the freshest editor-selected resources.
  • Visit Ask the Experts for answers to your Web services, SOAP, WSDL, XML, .NET, Java and EAI questions.
  • Couldn't attend one of our Webcasts? Don't miss out. Visit our archive to watch at your own convenience.
  • Choking on the alphabet soup of industry acronyms? Visit our helpful Glossary for the latest lingo.
  • Discuss this article, voice your opinion or talk with your peers in the SearchWebServices Discussion Forums.
This was last published in December 2003

Dig Deeper on Service orchestration

PRO+

Content

Find more PRO+ content and other member only offers, here.

Start the conversation

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.

-ADS BY GOOGLE

SearchSoftwareQuality

SearchCloudApplications

SearchAWS

TheServerSide.com

SearchWinDevelopment

DevOpsAgenda

Close