Distributed Architecture: Part 2 - Do you include messaging into your SOA? If not then you don't have a SOA!

by Michael Hodgdon posted on December 15 2010 01:45



I was pretty amazed by a presentation given by Udi Dahan. Udi focuses on addressing where the industry missed the boat with SOA.  He essentially says that a majority of the “SOA” implementations out there are nothing more than glorified RPC systems.  The idea being that contracts and schemas are great, but if you are dependent and synchronous in your calls you are chaining way too much.  If any service breaks down in that chain your SOA tenants are completely missed.  I will let his talk speak for the work as it’s his work and not mine J.  A summary of how messaging fulfills the SOA tenants is as follows:

Autonomous – By passing messages and handling requests and responses out of band you keep all of your services isolated and autonomous.

Schemas and Content – Because you are working with messages and the data that is within them (i.e. contracts) you have this by default.  The topic is messages that are passed through the infrastructure. Boundaries – Messages being the topic sent through the infrascture allow you to maintain policy and routing based on those messages.  This allows you to maintain boundaries and can keep your services fenced.

Follow this link to find his talk on msdn.

Tags: ,

Comments

Add comment


(Will show your Gravatar icon)

  Country flag

Click to change captcha
biuquote
  • Comment
  • Preview
Loading



Contact Us

We want to hear from you.  Our community is important to us and we want to make sure we give you the contact you want.  Please contact our team if you want to sent us feedback of any kind.  Enjoy reading!

RecentComments

Comment RSS