IBM and Microsoft recently launched another Web services-related effort - the
Web Services Interoperability Organization (www.ws-i.org), or WS-I for short.
Its charter is to promote Web services interoperability across platforms,
operating systems, and programming languages. I, for one, view
interoperability as absolutely critical to the success of Web services
technology. I don't think I'm alone in the view, since more than 60 companies
joined the consortium within the first week. Obviously the formation of this
group is a "good thing."
So I was a bit amused by the immediate defensive response that occurred after
the announcement. How does WS-I relate to the World Wide Web Consortium (W3C
- www.w3.org)? Isn't W3C supposed to define the interoperability standards?
And what about the SOAPBuilders group
(http://groups.yahoo.com/group/soapbuilders)? Aren't they taking... (more)
When discussing Web services, most people tend to focus on the core Web
services framework (the standards and protocols) and the applications that
you can build with the framework. Although I have no trouble waxing profusely
on these topics, I get even more jazzed when I start to think about
infrastructure-level Web services. (I know. I need to get a life.)
Infrastructure-level Web services are Web services that implement part of the
distributed computing infrastructure. They help other Web services
communicate. In particular, these services make the Web services framework
more ... (more)
There are many compelling reasons to use Web services. It seems as if
everyone is at least playing with Web services. Almost every software vendor
is building support for Web services into its platforms, languages, and
tools. Web services enable any-to-any integration, supporting any programming
language, any runtime platform, and any network transport. Technologies such
as SOAP and WSDL are simpler to use than traditional integration middleware
technologies, and they offer much more flexibility. When combined with
domain-specific industry standards, Web services enable unprecede... (more)
There is an old saying among standards wonks: "The most wonderful thing about
standards is that there are so many of them." And this truism is more
applicable today than ever before. There are so many WS-* specifications,
I've started referring to them as WS-Vertigo.
But there is a reason that there are so many of them. The Web Services
Framework (WSF) relies on a composable architecture. One of the primary
tenets of the WSF is to keep things as simple as possible. Therefore, if an
application doesn't require security, reliability, or transactions, you
shouldn't clutter up the i... (more)
UDDI (Universal Description, Discovery and Integration) is a registry for Web
services. It provides a mechanism to advertise and discover Web services.
Although you don't need to use UDDI to implement a Web services solution,
you'll find that a UDDI registry greatly simplifies the management and
administration of your services, particularly once they have reached a
certain critical mass.
Once you've developed more than a few services, and once you start giving
access to those services to more than a few controlled individuals,
management starts to get more challenging. Potential... (more)