What are noisy tenants?

#Introduction

Noisy tenants refer to clients or users in a shared environment that consume disproportionate resources, leading to performance degradation for other users. This document outlines the implications of noisy tenants and provides solutions to mitigate their impact.

#Necessary Cookies

#Performance Cookies

[Performance] ### Advertising Cookies [Advertising] ### Uncategorized Cookies [Uncategorized] Other uncategorized cookies are those that are being analyzed and have not yet been classified into a category. No cookies to display.

#User Options

• [Reject]
• [Save my settings]
• [Accept all]

Powered by

#Senior System Design

#How It Looks in Practice

For example, you are using a message broker (SQS, RabbitMQ…) and one tenant generates a large number of events. Since the broker and event handlers are shared, they mostly handle messages from the noisy tenant, while other clients suffer from increased latency.

Another example related to third-party integrations: You did not set clear rate limits for clients, and the noisy tenant calls a third-party API so frequently that it quickly exhausts all limits, preventing other clients from fully utilizing the integrations.

#Main Causes

1. Shared infrastructure: message brokers, databases, servers, etc.
2. Shared limits of external services or lack of rate limiting
3. Uneven traffic distribution

#Examples of Solutions

1. Limits and fair resource distribution
2. Implementing quotas for heavy and costly operations
3. Allocating separate resources for “fat” clients