I decide to write a short series of blog post on SOA patterns. These are not patterns that are only usable for SOA, however, I have found them particularly useful in implementing SOAs.

This isn’t an exhaustive list of pattern - on the contrary I'll try not repeat patterns which are well known (like  Entity Aggregation  http://patternshare.org/default.aspx/Home.PP.EntityAggregation )

I am a little busy these days (e.g. I have to complete an architecture document for one of my projects) - so this post will only introduce the (first batch of) patterns . And the following posts (in the series) will expand on each one (i.e. explain  What to do, usage context, consequences etc.). Then, if I'll get good feedback maybe I'll publish some more.

So, what patterns are we talking about here?

Well:

• Gateway - How do you scale a service without exposing too many endpoints?

• Inversion of Communication - How do I get the data from other services without too much coupling?

• Biztalkize - How do I control volatile behavior inside the  service ?

• Aggregated Reporting - How do you get a decent cross business entities report with the data scattered about in all those services?

• Transparent Emergence - How do I know where to find a service?

• Decoupled invocation - How can I handle peaks and high-loads without my service failing?

• Orchestrated Choreography  - How do I expand the behavior of hard-to-change service (e.g. legacy systems exposed as services) ?

Well, I hope this sparkle enough interest to make you follow the rest of the posts on this subject :)