http://www.soabloke.com/2008/09/20/the-architectural-role-of-messaging/ pushing soa up the slope (with a pointy stick) Wed, 04 Aug 2010 15:33:11 -0700 hourly 1 http://wordpress.org/?v=3.0.1 http://www.soabloke.com/2008/09/20/the-architectural-role-of-messaging/comment-page-1/#comment-567 The Power of Later | soabloke Tue, 05 May 2009 12:54:22 +0000 http://www.soabloke.com/2008/09/20/the-architectural-role-of-messaging/#comment-567 [...] client submits the request to a proxy (such as a message queue) and then carries on with other work. The service responds when it can and hopefully the response [...] [...] client submits the request to a proxy (such as a message queue) and then carries on with other work. The service responds when it can and hopefully the response [...]

]]> http://www.soabloke.com/2008/09/20/the-architectural-role-of-messaging/comment-page-1/#comment-560 Ian Robinson on Coupling | soabloke Tue, 28 Apr 2009 13:01:14 +0000 http://www.soabloke.com/2008/09/20/the-architectural-role-of-messaging/#comment-560 [...] coupling is possibly the most common architectural problem I see in many distributed systems. The manner in which system components interact can be a chief determinant of the scalability and reliability of the final [...] [...] coupling is possibly the most common architectural problem I see in many distributed systems. The manner in which system components interact can be a chief determinant of the scalability and reliability of the final [...]

]]>