0% found this document useful (0 votes)
17 views46 pages

Queue-Based Load Leveling Guide

Uploaded by

hamedur rahiman
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
17 views46 pages

Queue-Based Load Leveling Guide

Uploaded by

hamedur rahiman
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 46

Queue-Based Load

Leveling Pattern
What is Queue-Based Load Leveling Pattern?
What is Queue-Based Load Leveling Pattern?
 Category
 Messaging
 Reliability
 Resiliency
 Performance Efficiency
What is Queue-Based Load Leveling Pattern?
 Category
 Messaging
 Reliability
 Resiliency
 Performance Efficiency

 Use a queue that acts as a buffer between a task and a service it invokes
What is Queue-Based Load Leveling Pattern?
 Category
 Messaging
 Reliability
 Resiliency
 Performance Efficiency

 Use a queue that acts as a buffer between a task and a service it invokes

 Related Patterns
What is Queue-Based Load Leveling Pattern?
 Category
 Messaging
 Reliability
 Resiliency
 Performance Efficiency

 Use a queue that acts as a buffer between a task and a service it invokes

 Related Patterns
 Competing Consumer Pattern
What is Queue-Based Load Leveling Pattern?
 Category
 Messaging
 Reliability
 Resiliency
 Performance Efficiency

 Use a queue that acts as a buffer between a task and a service it invokes

 Related Patterns
 Competing Consumer Pattern
 Throttling Pattern
Service
Service
Service
Service
Service
Service
Service
Service
Service
Service
Service
Service
Service
Service
Service
Service
Service
Service
Service
Service
Service
Service
Service
Service
Service
Withdraw: 100$
Service
Balance: 100$

Withdraw: 100$
Service
Balance: 100$

Service

Withdraw: 100$
Balance: 100$

Withdraw: 50$
Service

Withdraw: 100$
Considerations
Considerations
 Avoid overwhelming the target resource.
Considerations
 Avoid overwhelming the target resource.

 Message queues are a one-way communication mechanism.


Considerations
 Avoid overwhelming the target resource.

 Message queues are a one-way communication mechanism.

 Be careful if you apply autoscalling to services that are listening for requests on the queue.
When to use this pattern?
When to use this pattern?

 This pattern is useful to any application that uses services that are subject to
overloading.
When NOT to use this pattern?
When NOT to use this pattern?

 This pattern isn't useful if the application expects a response from the service
with minimal latency.
Thank You!

You might also like