A few people who have been reading my blog and this column, and listening to
my podcast, as well as reading other SOA blogs and articles, have become a
bit confused pertaining to the notions of:
SOA Reference Model(s) SOA Reference Architecture(s) And how all of this
works and plays with Enterprise Architecture I spent a few hours of my
weekend attempting to research and define these concepts a bit better, in
essence, taking everyone's opinions and normalizing them so they make better
sense. What I found were many of the same notions, defined differently, but
all attempting to solve the same problems. Seems to be a common theme within
the world of SOA, but I digress.
Indeed, there are many definitions for the above concepts (not those terms
specifically) that are now being defined by guys like me, standards
organizations such as OASIS and the Open Group, and vendors ... (more)
Although a number of standards exist for information interchange and process
definition, industry standards have yet to emerge for defining common
integration server and B2B integration server services such as routing, rules
processing, and transformation. In the absence of such standards, individual
vendors have created proprietary approaches to these basic
information-processing services. As a result, we are confronted with features
that are not interchangeable, require specialized training, and do not
provide a common framework of services.
Even as we begin to implement stand... (more)
As we look to make more practical use of Web services, the need has emerged
for a better user interface; one that's neither too fat nor too thin. An
interface that allows developers to make the most out of the client's native
features, while at the same time, not bogging the client down with services
that are better kept at the back end.
We call this new hybrid interface a rich client. A rich client is a small
piece of software that runs on the client to leverage and aggregate back-end
Web services, allowing them to appear as a single, unified, native
application. Indeed, a new ... (more)
As I work with corporate America, as well as the government, I'm finding that
services-oriented architectures (SOAs) are like snowflakes - no two are
alike. I'm also finding that everyone has their own definition of SOA, and
I've seen everything from messaging systems to portals called an SOA.
So, who's right? I'm not sure I'm ready to declare somebody's architecture as
non-SOA just yet;, however, there are some patterns that are emerging in
terms of types of SOAs. I like to refer to these patterns as levels, since
they have a tendency to move from the very primitive, or level 0, ... (more)
The notion of building bridges to service providers and managing the
interaction will become more commonplace in 2006 as we learn to accept that
many services we leverage within an enterprise are services we may not host.
The technology exists today. We need to define and refine our approaches now,
including architectures, enabling technology, and use of standards. Most
enterprises are way behind.
We are moving toward a day when most of our enterprise applications may be
delivered as services, and thus provide a more economical way to approach
information technology management w... (more)