﻿<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Ayende @ Rahien</title><link>http://ayende.com</link><description>Ayende @ Rahien</description><copyright>Copyright (C) Ayende Rahien  2004 - 2021 (c) 2026</copyright><ttl>60</ttl><item><title>Nigel Holland commented on Asynchronous order processing</title><description>I can give two good reasons for asynchronous order processing.
  
  
1. Resilience, you can bring down any part of your order processing system but still keep capturing orders.
  
  
2. Smoothing out processing spikes, if captured orders are queued for processing you can smooth out the load on your order processing system.
  
</description><link>http://ayende.com/4068/asynchronous-order-processing#comment10</link><guid>http://ayende.com/4068/asynchronous-order-processing#comment10</guid><pubDate>Tue, 04 Aug 2009 15:31:40 GMT</pubDate></item><item><title>firefly commented on Asynchronous order processing</title><description>Nice! I like your post, simple and to the point. I think Amazon is one of the best website out there. 5 minutes is a very reasonable time. Yet I imagine that little window allow the server to process the request in a much efficient manner.
</description><link>http://ayende.com/4068/asynchronous-order-processing#comment9</link><guid>http://ayende.com/4068/asynchronous-order-processing#comment9</guid><pubDate>Tue, 14 Jul 2009 22:19:45 GMT</pubDate></item><item><title>Shane Courtrille commented on Asynchronous order processing</title><description>O'Reilly Safari also uses the same trick for downloading PDFs.
</description><link>http://ayende.com/4068/asynchronous-order-processing#comment8</link><guid>http://ayende.com/4068/asynchronous-order-processing#comment8</guid><pubDate>Tue, 14 Jul 2009 17:07:10 GMT</pubDate></item><item><title>Daniel commented on Asynchronous order processing</title><description>I think where this type of architecture is difficult for people to understand is in typical forms-on-data and search scenarios.  For example: Google does not show a "processing your search" page - you simply enter something and the results appear.  Similarly, if you enter some bit of data to a form and click 'save', you expect it to appear next time you refresh the list.  For example, when you add an item to your cart on Amazon, it appears instantly in your cart.  These are the sort of transactions that can be a bugger in a medium load app, but that I still can't get my head around writing asynchronously. 
  
  
As somebody interested in ESB tech, but struggling to apply it, what I'd really love to see is a reference app like Nerd Dinner or Rob's MVC Storefront re-done with these concepts.
  
</description><link>http://ayende.com/4068/asynchronous-order-processing#comment7</link><guid>http://ayende.com/4068/asynchronous-order-processing#comment7</guid><pubDate>Tue, 14 Jul 2009 15:38:52 GMT</pubDate></item><item><title>josh commented on Asynchronous order processing</title><description>checking how something is done in general is standard practice for me, but you also have to know when to follow and when to lead. I think Amazon does a lot of things well, but wouldn't follow their example in every case or circumstance.
</description><link>http://ayende.com/4068/asynchronous-order-processing#comment6</link><guid>http://ayende.com/4068/asynchronous-order-processing#comment6</guid><pubDate>Tue, 14 Jul 2009 15:25:11 GMT</pubDate></item><item><title>Jo&amp;#227;o P. Bragan&amp;#231;a commented on Asynchronous order processing</title><description>Asynchronicity is how the world works! The fastest any feedback loop can operate is at the speed of light. Porting everything over to ESB has made my life a lot easier.
</description><link>http://ayende.com/4068/asynchronous-order-processing#comment5</link><guid>http://ayende.com/4068/asynchronous-order-processing#comment5</guid><pubDate>Tue, 14 Jul 2009 15:12:55 GMT</pubDate></item><item><title>NotMyself commented on Asynchronous order processing</title><description>I hate to say it but I have won several UI arguments recently with "Let's see how google handles this." And then finding an example of what I was talking about in the google environment somewhere.. either mail, docs or reader...
</description><link>http://ayende.com/4068/asynchronous-order-processing#comment4</link><guid>http://ayende.com/4068/asynchronous-order-processing#comment4</guid><pubDate>Tue, 14 Jul 2009 14:50:52 GMT</pubDate></item><item><title>Daniel Auger commented on Asynchronous order processing</title><description>I use Amazon a lot to sway thinking/get buy in on design decisions. There are very few things Amazon does wrong IMHO. I rarely hear complaints from friends/family about the way the site works.
</description><link>http://ayende.com/4068/asynchronous-order-processing#comment3</link><guid>http://ayende.com/4068/asynchronous-order-processing#comment3</guid><pubDate>Tue, 14 Jul 2009 14:26:11 GMT</pubDate></item><item><title>Kyle Szklenski commented on Asynchronous order processing</title><description>There's a big difference between pointing out a good reason to do something, showing that it's done on a popular website, and arguing from authority. If Amazon had a crappy website that was badly designed and had no functionality, then your argument would have no weight. However, when you go to an expert in the field of something and use their arguments, it's not an argument from authority, or at least not a bad one - it is perfectly valid, because that person/entity has the knowledge and understanding of the field.
</description><link>http://ayende.com/4068/asynchronous-order-processing#comment2</link><guid>http://ayende.com/4068/asynchronous-order-processing#comment2</guid><pubDate>Tue, 14 Jul 2009 13:00:47 GMT</pubDate></item><item><title>Rafal commented on Asynchronous order processing</title><description>This vampire fascination is something new, isn't it? Hope your recent vacation wasn't anywhere near Transylvania..
</description><link>http://ayende.com/4068/asynchronous-order-processing#comment1</link><guid>http://ayende.com/4068/asynchronous-order-processing#comment1</guid><pubDate>Tue, 14 Jul 2009 11:27:20 GMT</pubDate></item></channel></rss>