Wise words. Thanks. I'll try to keep an open mind about MQs. Personally I know I'm probably only going to really understand it by actually building something with it. I'm not very academic.
This is really cool!
Something funny I've noticed at Mozilla is that "message queueing" and the worker model are conflated. I first noticed this when I learned that our web clusters' rabbitmq hosts are named "celery", even though they're only running rabbitmq.
Message queueing can be used for so much more than the worker model. You can use it to implement shared state (using Paxos if you want to get fancy). You can build multi-user games with it. You can build APIs around it to allow different applications to communicate - the classic example being sales and billing.
It's a little thing, I know, but I'd hate to see the webdev community miss the forest for the trees by thinking that MQ is *just* the worker model. It's *so* much more.
Comment
Wise words. Thanks. I'll try to keep an open mind about MQs. Personally I know I'm probably only going to really understand it by actually building something with it. I'm not very academic.
Parent comment
This is really cool! Something funny I've noticed at Mozilla is that "message queueing" and the worker model are conflated. I first noticed this when I learned that our web clusters' rabbitmq hosts are named "celery", even though they're only running rabbitmq. Message queueing can be used for so much more than the worker model. You can use it to implement shared state (using Paxos if you want to get fancy). You can build multi-user games with it. You can build APIs around it to allow different applications to communicate - the classic example being sales and billing. It's a little thing, I know, but I'd hate to see the webdev community miss the forest for the trees by thinking that MQ is *just* the worker model. It's *so* much more.