Sometimes when we're faced with addressing a complex engineering problem it's
helpful to reflect on antipatterns. Doing so does more than track wrong
solutions to common problems; it also focuses the mind on the interaction of
the most important elements of the problem domain. This is true for all
engineering, not just software engineering. Suspension bridge designers know
to be on the lookout for torsional oscillations because of the collapse of
the Tacoma Narrows Bridge, but they also better understand the importance of
stiffening the structure in general. The goal is to limit the number of times
the antipattern emerges and to notice it when it comes around again. SOA
uptake is at a point where such a treatment of antipatterns is helpful.
In my job I work with Fortune-... (more)
Part I of this series observed that 2006 was the year in which many
large-scale SOA projects were kicked off in medium and large enterprises.
Which means that an all-encompassing methodology that could evolve SOA to the
enterprise was needed. Much has been written about service analysis and
design for SOA but not so much about methodologies for creating an
all-encompassing SOA, including... (more)
I'm sure I'm like many of you in this respect: I got into engineering because
I love the idea of being able to address complex problems with a combination
of my talent, my friends' talent, and the tools that I can come up with to
make our work as easy as possible (work smart not hard!). It is this approach
that has guided me in my work as an application and technical architect. I
come to... (more)
Many enterprises are currently reorganizing their people, processes, and
technology around services. A few are holistically revamping their enterprise
architectures around SOA and embarking on roadmaps to achieve grandiose
business goals.
Far more enterprises are trying to deal with the unexpected emergence of
services and service integration requirements resulting from platform
upgrade... (more)
I know what you're thinking: SOA hype has reached an absurd level and now
someone is literally proclaiming that it will change the world - but bear
with me for a minute. Anyone who has been around corporate IT for the last
five years or so has seen an avalanche of development work sent offshore for
two primary reasons: cheaper unit labor cost and the flat-out inability to
find qualified ... (more)
Paul O'Connor is SOA Practice Director and Chief SOA Architect for e-brilliance LLC (a leading NE SOA consultancy), and is currently doing major SOA architecture and implementations for Fortune 100 clients across the US. Previously he was chief architect for Damascus Road Systems, specializing in security architecture.
Alf Pilgrim
Per Sjofors
Kirsten Lytsen
Data Recovery Services
Colin Armitage
