Every now and then I get some question by email, I usually just answer them directly but considering I got 2 such questions this week and that I have’t blogged for awhile (I do have a post about YARN which I hope to finish soon) – I thought I’d also publish my replies here.
Question #1 from Simon:
In your very interesting article “Bridging the Impedance Mismatch Between Business Intelligence and Service-Oriented Architecture” you highlight the challenges for BI and SOA to co-exist – that was 6 or so years ago – have you seen any advances that would cause you to revise that view?
I think the gap and dissonance between SOA needs and BI needs is still there. However, in addition to event publishing mentioned in the article, I see the approach to getting to BI on SOA getting more standardized. … Read More »
I want to say I am delighted but I guess relieved is the right word here - I’ve finally submitted all the book chapters to manning and I’m now doing an editing round on all the chapters (re-adding missing images, update pattern references, fixing typos etc.).
The current (and hopefully final) table of contents is as follows:
Part I – SOA Patterns
Chapter 1 – Solving SOA pains with patterns – an introduction
Chapter 2 – Basic structural patterns
Chapter 3 – Performance, scalability and availability patterns
Chapter 4 – Security and manageability patterns
Chapter 5 – Message exchange patterns
Chapter 6 – Service consumer interaction patterns
Chapter 7 – Service integration patterns
part II – SOA in the real world
Chapter 8 – SOA anti-patterns
Chapter 9 – Putting it all together – a case study
Chapter 10 – SOA vs. the world – how SOA fits with other techs: REST, Cloud and Big data
As part … Read More »
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 … Read More »
It all starts with a business requirement – as it always should. We have an ordering system (say the same one from the Knot anti-pattern) and the business says they only want to confirm an order to the user if the item is already secured for that order in the stock. From the technical point of view we have 2 separate services – one handles orders the other handles the stock – now what?
Figure 10.1 A vanilla ordering scenario. An Ordering service needs to confirm item in stock before confirming order for customer.
This sounds like a text book case for using transactions but in reality it isn’t. I am going to explain why in a short while but before we go there let’s do a (very) short recap on transactions and distributed transactions.
Transactions basically build on four basic tenets: … Read More »
The formatting on the html version of the nano-services is a bit off (Word to HTML is so much fun) so I am also making it available as PDF.
if you don’t remember
Nonoservice is an Anti-pattern where a service is too fine grained. Nanoservice is a service whose overhead (communications, maintenance etc.) out-weights its utility.
* illustration by verzerk