✳flâneur — a map of the web's best reading

System Design, Chapter 7: Queues

charlieinden.github.io · 995 words · saved by 1 readers

Let’s start by defining message queues; how you can use a message queue and the benefits achieved when using message queues. A queue is a line of things waiting to be handled — in sequential order starting at the beginning of the line. A message queue is a queue of messages sent between applications. It includes a sequence of work objects that are waiting to be processed. A message is the data transported between the sender and the receiver application; it’s essentially a byte array with some headers on top. An example of a message could be an event. One application tells another application to start processing a specific task via the queue. The basic architecture of a message queue is simple; there are client applications called producers that create messages and deliver them to the message queue. Another application, called a consumer, connects to the queue and gets the messages to be processed. Messages placed onto the queue are stored until the consumer retrieves them. Processing Q

For previous chapter — System Design, Chapter 6: Proxies System Design, Chapter 7: Queues For previous chapter — System Design, Chapter 6: Proxies --> What is message queuing? Let’s start by defining message queues; how you can use a message queue and the benefits achieved when using message queues. A queue is a line of things waiting to be handled — in sequential order starting at the beginning of the line. A message queue is a queue of messages sent between applications. It includes a sequence of work objects that are waiting to be processed. A message is the data transported between the sen

Explore this link on the map →

related reading