This post originated from an RSS feed registered with .NET Buzz
by Udi Dahan.
Original Post: Devx SOA Article published for IBM
Feed Title: Udi Dahan - The Software Simplist
Feed URL: http://feeds.feedburner.com/UdiDahan-TheSoftwareSimplist
Feed Description: I am a software simplist. I make this beast of architecting, analysing, designing, developing, testing, managing, deploying software systems simple.
This blog is about how I do it.
My latest article "SOA Support, SOA Therapy, SOA Treatment" (http://www.devx.com/ibm/Article/29325 ) has just been published for the IBM section of DevX. Please leave comments here, though. As for orchestration, which was subtely(?) editted out, my thoughts are as follows: If you have a bus-style architecture, orchestration/choreography is out. If you have a broker-style architecture, you could try it. On the other hand, orchestration will only be good for the broker, all the other spoke-services are out. And if you understand what Activities really are (long running business processes is such a misnomer), you could implement them yourself with such a performance gain that you'd laugh at the benchmarks all the vendors are pushing....