Queue: Basic Overview

Download this episode

Download Video

Description

A quick overview of a web application, with the introduction of a queue.

 

Have any questions for Jef?

Contact him via Twitter

Tags:

Azure, Queue

Embed

Format

Available formats for this video:

Actual format may change based on video formats available and browser capability.

    The Discussion

    • User profile image
      js8229

      Great first post... can't wait to see more of this coming in the future.  Regarding the queuing mechanism to scale web application writes, how would more of an always-async technology like Node.js affect this choice vs. a typical single- or multi- thread web application?

    • User profile image
      JefKing

      @js8229:

      Async enables a server to handle more concurrent requests by suspending execution of a 'long running call'; or in this case when a message is being added to a queue. Async Vs. non-async doesn't affect my choice in when to use a queue. It might delay it slightly, but in a world where we can spin up more servers to handle concurrency; non-async can be scaled up to handle async throughput volumes (to some degree).

      I would introduce a queue when: additional latency is not a concern (determine what your threshold is), and secondly when your data store is potentially not able to handle your peak load (this typically requires load testing, and forcasting).

      Lastly, I don't want to discount async and languages like Node.js I think that it is the cats pajamas.[H]

    Comments closed

    Comments have been closed since this content was published more than 30 days ago, but if you'd like to send us feedback you can Contact Us.