With the unwavering prominence of service-oriented architecture (SOA) there
is an increasing interest in understanding what exactly it means for
something to be considered "service-oriented." Thomas Erl recently completed
a lengthy research project for SOA Systems Inc. into the origins of SOA and
the current state of service-orientation among all primary SOA technology
platforms. This body of work contributed to the mainstream SOA methodology
developed by SOA Systems and was also documented in Thomas's new book,
Service-Oriented Architecture: Concepts, Technology, and Design. We caught up
with Thomas (a previous contributor to WSJ) to ask him to share some of the
insights he gained from his work with SOA and service-orientation.
There's no need to mention that SOA has be... (more)
One of the fundamental goals when designing service-oriented solutions is to
attain a reduced degree of coupling between services, thereby increasing the
freedom and flexibility with which services can be individually evolved.
Achieving the right level of coupling "looseness" is most often considered a
design issue that revolves around the service contract and the consumer
programs that ... (more)
Originally inspired by techniques used to design buildings and cities, and
popularized by the Gang of Four during the mainstream emergence of
object-orientation, design patterns have seen us through the various shifts
in architecture, technology, and, of course, design. Pattern catalogs have
periodically emerged, one building on the other, and each revealing a set of
problem-solving tech... (more)
Enterprise-wide harmonization is a desirable and ideal target state that
fully supports pretty much everything SOA and service-orientation stand for.
For those that have achieved such a state, bless your standardized hearts.
You have accomplished something that has eluded many others. However, not
attaining this state does not mean you cannot successfully adopt SOA.
In some circles it has... (more)
Many are comparing notes on two well-publicized paths to achieving SOA. The
bottom-up approach is currently the most common variety, where Web services
are created on an "as need" basis to fulfill mostly integration-related
requirements. These services are typically application specific and simply
re-create traditional integration channels over the open Web services
communication framewo... (more)