Software Architecture Patterns, Antipatterns, and Pitfalls

Chapter 18. Supervisor Consumer Pattern

A Note for Early Release Readers

With Early Release ebooks, you get books in their earliest form—the author’s raw and unedited content as they write—so you can take advantage of these technologies long before the official release of these titles.

This will be the 32nd chapter of the final book. Please note that the GitHub repo will be made active later on.

If you’d like to be actively involved in reviewing and commenting on this draft, please reach out to the editor at [e-mail].

As companies grow and expand, their systems need to grow to support the increase in user load—in other words, they need to scale. Scalability is about a system being able to handle an increase in user load while maintaining a consistent response time for all users. The Supervisor Consumer pattern allows developers and architects to provide scalability within a service instance, allowing services to respond to multiple requests without having to create additional service instances.

Table 18-1 summarizes the metadata for the Supervisor Consumer pattern.

Table 18-1. Metadata for the Supervisor Consumer pattern

CATEGORY	METADATA
CONTEXT:	Event-Driven Architecture, Message-Based Architectures
IMPROVED:	Elasticity, Scalability, Responsiveness, Throughput
DEGRADED:	Message Order, Simplicity

How Can I Improve Message Throughput and Scalability?

In message-based and event-driven architectures that use asynchronous communication, bottlenecks form ...