Architecture Patterns for Enterprise-wide SOA

Borjan Cace, dinsdag 22 april 2008

Service Oriented Architecture has entered the mainstream of business applications and articles about SOA continue to proliferate. However, texts that share people’s real-life experiences with SOA are scarce. Partly this can be attributed to difficulties in sharing architectural knowledge in a structured way. This article calls for more effort to be put into sharing knowledge through architectural patterns. That is done by describing five concrete patterns that have emerged in the SOA practice of information-intensive enterprises. Fellow architects are invited to join the effort of ‘Via Nova Architectura’ and share their experiences through patterns.


Je moet lid zijn van Via Nova Architectura om reacties te kunnen toevoegen!

Wordt lid van Via Nova Architectura

Reactie van Stichting Digital Architecture op 6 Juni 2012 op 12.02

Geschreven door Mary Beijleveld op 29-04-2008 11:54

Hoi Borjan,

Goed stuk!. Ben blij dat ik regelmatig op deze website kijk.
In het kader van het kennismanagement, waar wij beiden zo verknocht aan zijn, zou het goed zijn als je deze paper met onze collega's deelt. Dat is niet afhankelijk van een goede instrument maar van (de wil om) gebruik (te maken) van beschikbare communicatiemiddelen. Volgens mij kijken onze collega's namelijk niet zo vaak op deze website. je zou ook kunnen melden dat je dit artikel op via nova architecture hebt geplubliceerd.

Reactie van Stichting Digital Architecture op 6 Juni 2012 op 12.02

Geschreven door Hans Oesterholt-Dijkema op 29-04-2008 20:32

Ja, prima stuk. Nog iemand die hier regelmatig eens komt kijken ;-).

Reactie van Stichting Digital Architecture op 6 Juni 2012 op 12.02

Geschreven door Richard van Schelven op 03-05-2008 23:23


An interesting article indeed. I can indeed also recommend the Thomas Erl site: I am looking forward to the patterns you and others in Via Nova Architectura will publish.

I have one question with respect to a statement you make: "Please note here that significant numbers of integration solutions were service oriented much before the term ‘Service Oriented Architecture’ has been introduced." Could you please elaborate on that. Are you saying that these integration solutions were for business which were themselves service oriented?

With kind regards,


Reactie van Stichting Digital Architecture op 6 Juni 2012 op 12.01

Geschreven door Borjan Cace op 01-06-2008 19:59

I apologize for not reacting more promptly; have been on vacation for two weeks …
The SOA precursors I'm referring to are solutions that were produced at some large telecom firms. Saying this, I'm not excluding other efforts that have led to SOA – it is merely that I do know about some and not about others.
Anyway, the integration solutions created in two projects I’ve been involved with (both started before the acronym SOA came to life) have been entirely service oriented, so I’ll elaborate on those. Again, there have been others, for sure. SOA is a pattern, and patterns come to life evolutionary.
One of the business problems has been how to facilitate product delivery via own outlet stores and later via outlet stores AND other channels like call centers and intermediate retailers. The customer database, stock inventory (phones, other devices, cables, …), billing, workforce planning etc, all these systems were required to be accessible from the call centre application and the applications supporting the outlet store employees (having employees accessing each system separately has been causing serious problems).
In the projects I’ve been involved, the systems were interacting via Tuxedo ( on-line messaging and the Tuxedo environment has been extended by a number of custom made adapters (hub-and-spoke integration style). Additionally, to make the solution sustainable, the interfaces were controlled centrally, on the enterprise level. This was accomplished by augmenting the technique of Tuxedo through introduction of formal contracts conforming to the guidelines of the OSCA architecture of Bellcore.
OSCA proscribed contracts between ‘building blocks’ of the solution. The contracts were specifying the formal interfaces (parameters) but also preconditions, post-conditions, semantics and the QoS aspects of interactions. Of course, there were neither open standards nor commercial products to support this (XML wasn’t there, for example). Nonetheless, the loose coupling of Tuxedo augmented by the contract formalism of OSCA worked well in practice.
To me, OSCA was really visionary. Most unfortunately, the successor of Bellcore, Telcordia, does not allow free access to any, even really old and most likely commercially obsolete documents. Some OSCA articles may be illegally available on Internet (like the article from 1990, ‘The OSCA™ Architecture, Enabling Independent product software maintenance’). Someone interested into that piece of SOA history should visit the Telcordia Technical Document Center and then check ‘Distributed Interoperable & Operable Computing Environment and Systems (DIOCES)’ (; KEYWORDS=Distributed+Interoperable+%26+Operable+Computing+En vironment+and+Systems+(DIOCES)&TITLE=&DOCUMENT=&DATE=&CLASS=PS42&COUNT=1000#TR). There you can find documents like ‘OSCA(TM) Contract Specification Guidelines’ etc.

Reactie van Stichting Digital Architecture op 6 Juni 2012 op 12.01

Geschreven door Raoef Hussainali op 17-06-2008 12:34

Beste Borjan,

Ik wil je complimenteren met dit non hand waving in depth expertise value adding article. That's all.

Dank en groet,



© 2020   Gemaakt door Stichting Digital Architecture.   Verzorgd door

Banners  |  Een probleem rapporteren?  |  Algemene voorwaarden