{"id":"asynchronism","title":"Asynchronism","sections":[{"id":"overview","title":"Overview","html":"

\n \"Diagram\"\n
\n Source: Intro to architecting systems for scale\n

\n

Asynchronous workflows help reduce request times for expensive operations that would otherwise be performed in-line. They can also help by doing time-consuming work in advance, such as periodic aggregation of data.

","headings":[]},{"id":"message-queues","title":"Message queues","html":"

Message queues

\n

Message queues receive, hold, and deliver messages. If an operation is too slow to perform inline, you can use a message queue with the following workflow:

\n\n

The user is not blocked and the job is processed in the background. During this time, the client might optionally do a small amount of processing to make it seem like the task has completed. For example, if posting a tweet, the tweet could be instantly posted to your timeline, but it could take some time before your tweet is actually delivered to all of your followers.

\n

Redis is useful as a simple message broker but messages can be lost.

\n

RabbitMQ is popular but requires you to adapt to the 'AMQP' protocol and manage your own nodes.

\n

Amazon SQS is hosted but can have high latency and has the possibility of messages being delivered twice.

","headings":[{"id":"message-queues","title":"Message queues","depth":3}]},{"id":"task-queues","title":"Task queues","html":"

Task queues

\n

Tasks queues receive tasks and their related data, runs them, then delivers their results. They can support scheduling and can be used to run computationally-intensive jobs in the background.

\n

Celery has support for scheduling and primarily has python support.

","headings":[{"id":"task-queues","title":"Task queues","depth":3}]},{"id":"back-pressure","title":"Back pressure","html":"

Back pressure

\n

If queues start to grow significantly, the queue size can become larger than memory, resulting in cache misses, disk reads, and even slower performance. Back pressure can help by limiting the queue size, thereby maintaining a high throughput rate and good response times for jobs already in the queue. Once the queue fills up, clients get a server busy or HTTP 503 status code to try again later. Clients can retry the request at a later time, perhaps with exponential backoff.

\n

Disadvantage(s): asynchronism

\n\n

Source(s) and further reading

\n","headings":[{"id":"back-pressure","title":"Back pressure","depth":3},{"id":"disadvantages-asynchronism","title":"Disadvantage(s): asynchronism","depth":3},{"id":"sources-and-further-reading-11","title":"Source(s) and further reading","depth":3}]}],"sourceFiles":[]}