First off, In the previous post I published the Transactional Integration anti-pattern – if you need it for off-line reading you can also get it in PDF form.

I am currently writing the “3-tier SOA” anti-pattern and it seems that together with “Whitebox services” anti-pattern it will complete the anti-patterns chapter. The two other anti-patterns in the chapter are Nanoservices and the Knot

I’ve also started writing the composite-front end pattern (e.g. portals, prism etc.) but mid-way I thought about it and stopped. I basically realized that there are a few patterns that are pretty common to SOA on one hand, but you are much more likely to use a 3rd party solution that includes them than to realize them yourself. These include the composite front-end mentioned above, repository, orchestration, servicebus, service host that appears in chapter 2 (though I think that is marginal case) and maybe a couple of others. I am thinking in moving these to an “SOA infrastructure patterns” chapter. The open question I still have is would they need the same structure and depth as the other patterns. For example it might beneficial to emphasis usage, or expand the technology mapping etc.

As always, any comments are welcomed

By the way, if you are struggling with the architecture of your distributed system/SOA, I’d be more than happy to help you sort things out