Comments on: Mixing async and sync in distributed systems http://lostechies.com/jimmybogard/2012/05/15/mixing-async-and-sync-in-distributed-systems/ Strong opinions, weakly held Fri, 17 May 2013 09:02:38 +0000 hourly 1 http://wordpress.org/?v=3.4.2 By: Crodriguez http://lostechies.com/jimmybogard/2012/05/15/mixing-async-and-sync-in-distributed-systems/#comment-4617 Crodriguez Fri, 25 May 2012 11:11:00 +0000 http://lostechies.com/jimmybogard/2012/05/15/mixing-async-and-sync-in-distributed-systems/#comment-4617 Jimmy!! Tag search still not working! Sorry to bother man, but this stuff is so good but so hard to find... If you want tell me and I email someone or whatever. Thank you Jimmy!! Tag search still not working! Sorry to bother man, but this stuff is so good but so hard to find… If you want tell me and I email someone or whatever.
Thank you

]]> By: Nathan Alden http://lostechies.com/jimmybogard/2012/05/15/mixing-async-and-sync-in-distributed-systems/#comment-4609 Nathan Alden Tue, 22 May 2012 16:29:00 +0000 http://lostechies.com/jimmybogard/2012/05/15/mixing-async-and-sync-in-distributed-systems/#comment-4609 As you're implying, I think the important takeaway here isn't necessarily synchronous vs. asynchronous but rather internal vs external systems. Communicating with third-parties means a whole host of potential pitfalls--pitfalls that can be overcome by using an asynchronous messaging architecture instead of in-proc calls. When writing code, it's a good idea to consider if one will have to deal with potentially unreliable external systems. If external systems are present, interface with them through a technology like NServiceBus instead of the usual "do everything in the Web request thread" approach. Get that messaging architecture in place early and avoid the temptation to do all work in the Web request thread! As you’re implying, I think the important takeaway here isn’t necessarily synchronous vs. asynchronous but rather internal vs external systems. Communicating with third-parties means a whole host of potential pitfalls–pitfalls that can be overcome by using an asynchronous messaging architecture instead of in-proc calls.

When writing code, it’s a good idea to consider if one will have to deal with potentially unreliable external systems. If external systems are present, interface with them through a technology like NServiceBus instead of the usual “do everything in the Web request thread” approach. Get that messaging architecture in place early and avoid the temptation to do all work in the Web request thread!

]]> By: Distributed Weekly 155 — Scott Banwart's Blog http://lostechies.com/jimmybogard/2012/05/15/mixing-async-and-sync-in-distributed-systems/#comment-4603 Distributed Weekly 155 — Scott Banwart's Blog Fri, 18 May 2012 13:22:03 +0000 http://lostechies.com/jimmybogard/2012/05/15/mixing-async-and-sync-in-distributed-systems/#comment-4603 [...] Mixing async and sync in distributed systems [...] [...] Mixing async and sync in distributed systems [...]

]]> By: The Morning Brew - Chris Alcock » The Morning Brew #1106 http://lostechies.com/jimmybogard/2012/05/15/mixing-async-and-sync-in-distributed-systems/#comment-4602 The Morning Brew - Chris Alcock » The Morning Brew #1106 Wed, 16 May 2012 08:47:52 +0000 http://lostechies.com/jimmybogard/2012/05/15/mixing-async-and-sync-in-distributed-systems/#comment-4602 [...] Mixing async and sync in distributed systems - Jimmy Bogard discusses user expectations of how systems work, and how this can make having parts of your system work in a more async way difficult, taking a look at how you can go about making operations async in a CQRS environment. [...] [...] Mixing async and sync in distributed systems – Jimmy Bogard discusses user expectations of how systems work, and how this can make having parts of your system work in a more async way difficult, taking a look at how you can go about making operations async in a CQRS environment. [...]

]]>