I realized that I had been using a reference model, in my head, for a long time when describing the ‘moving parts’ in a Service Oriented Architecture.  It was time to put those items into a diagram and share it around.  So, here’s the current diagram.

In this diagram, I illustrate the distinctions between:

Transitive Transaction Store and Services

Domain Data Management, Repository, and Services

Thin Consumer, Rich Consumer, Extended Consumer, Proxy Consumer

Floating Services

Large Object Messaging Service

I don’t go into a lot of detail outside the diagram (here in the blog post).  I may add another post to follow up.  Comments are very welcome. (click the thumbnail view to enlarge)


By Nick Malik

Former CIO and present Strategic Architect, Nick Malik is a Seattle based business and technology advisor with over 30 years of professional experience in management, systems, and technology. He is the co-author of the influential paper "Perspectives on Enterprise Architecture" with Dr. Brian Cameron that effectively defined modern Enterprise Architecture practices, and he is frequent speaker at public gatherings on Enterprise Architecture and related topics. He coauthored a book on Visual Storytelling with Martin Sykes and Mark West titled "Stories That Move Mountains".

3 thoughts on “A SOA Infrastructure Reference Model”

Leave a Reply

Your email address will not be published. Required fields are marked *

3 × 4 =

This site uses Akismet to reduce spam. Learn how your comment data is processed.