Comments on: Asynchronous Processing in Web Applications, Part 1: A Database Is Not a Queue

By: Chris

Chris — Tue, 12 Mar 2013 11:26:38 +0000

Good work Nathan,

I have just been teaching some classes on basic development and I have been explaining the importance of starting from the ground up with their database functions…

I will point my next class in this direction for their homework.

By: Devops Weekly Digest 02/23 - pydelion.com

Devops Weekly Digest 02/23 - pydelion.com — Sat, 23 Feb 2013 14:02:22 +0000

[...] Asynchronous Processing in Web Applications, Part 1: A Database Is Not a Queue. [...]

By: Brad Wood

Brad Wood — Tue, 15 Jan 2013 16:39:50 +0000

“… the fastest route through your system has now been delayed to the sum of all the different polling intervals.”

Shouldn’t that read the *slowest* possible route through your system? That’s analagous to hitting every red light on the way to work right as they turn red.
The fastest possible route would be no wait at all, like hitting every single green light on the way to work.

I would say, the much more useful statistic is that the average time through the system would be the sum of half of each polling interval.

By: Asynchronous Processing in Web Applications, Part 2: Developers Need to Understand Message Queues

Tue, 08 Jan 2013 00:39:47 +0000

[...] the first part of this series, we explained asynchronous processing, when you might need to use it and why leveraging a database [...]

By: Mikhail Davidovich

Mikhail Davidovich — Fri, 21 Dec 2012 12:21:04 +0000

What you wanna say, bro?

By: Cynthia

Cynthia — Thu, 06 Dec 2012 20:29:24 +0000

It’s a pity you don’t have a donate button! I’d most certainly donate to this outstanding blog! I guess for now i’ll settle for bookmarking and
adding your RSS feed to my Google account. I look forward to brand new updates
and will talk about this blog with my Facebook group. Chat soon!

By: Артём Власов

Артём Власов — Sat, 24 Nov 2012 13:12:30 +0000

Мнение известного экономиста о МММ http://mmmrevolution.com/?m=content&id=86

By: trwww

trwww — Tue, 20 Nov 2012 05:50:18 +0000

You still need a place to store the state of the asynchronous processes so you can report and manipulate them from the web interface.

By: » Asynchronous Processing in Web Applications, Part 1: A Database Is Not a Queue Pete's Blog

Mon, 19 Nov 2012 19:17:16 +0000

[...] is making it’s way around the internal webernets is a multi-part series by Miso Engineering: Asynchronous Processing in Web Applications, Part 1: A Database Is Not a Queue. The article is an interesting read for those starting to expand their web application [...]

By: nathan

nathan — Thu, 15 Nov 2012 19:24:24 +0000

I am really glad you brought this up. This is something I will covering in greater detail in my next post. In the ruby ecosystem, Redis is used very frequently as a job queue to some success with resque https://github.com/defunkt/resque but that doesn’t mean redis is a true replacement for a MQ by any stretch. And I think by trying to replace the need for a true MQ with Redis, depending on requirements you may be missing out on more then initially realized in terms of long term scalability, job throughput, message delivery control, robust error handling, etc.