# Interning at incident.io: rate limiting, resiliently

DevFeed: [Interning at incident.io: rate limiting, resiliently](<https://devfeed.tech/articles/interning-at-incident-io-rate-limiting-resiliently-11848.md>)

Original publisher: [Read original article](<https://incident.io/blog/interning-at-incident-io-rate-limiting-resiliently>)

Author: Anthony Oparaocha

Published: 2026-09-02T10:33:13Z

Content type: article

Language: en

Sources: [The incident.io Blog](<https://devfeed.tech/sources/the-incident-io-blog.md>)

Topics: [incident](<https://devfeed.tech/topics/incident.md>), [systems](<https://devfeed.tech/topics/systems.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>), [dashboards](<https://devfeed.tech/topics/dashboards.md>)

Tags: [cloud](<https://devfeed.tech/tags/cloud.md>), [incident](<https://devfeed.tech/tags/incident.md>), [incident-channel](<https://devfeed.tech/tags/incident-channel.md>), [incident-management](<https://devfeed.tech/tags/incident-management.md>), [incident-response](<https://devfeed.tech/tags/incident-response.md>), [memory](<https://devfeed.tech/tags/memory.md>), [outage](<https://devfeed.tech/tags/outage.md>), [post-mortem](<https://devfeed.tech/tags/post-mortem.md>), [product](<https://devfeed.tech/tags/product.md>), [production](<https://devfeed.tech/tags/production.md>), [slack-incident](<https://devfeed.tech/tags/slack-incident.md>), [systems](<https://devfeed.tech/tags/systems.md>)

## AI overview

An incident.io intern describes making rate limiting resilient to the loss of its Valkey backing store. The solution used per-pod in-memory top-k buffers so the platform could continue rate limiting instead of failing open when Valkey became unavailable.

## Source excerpt

Our rate limiter depends on Valkey. If Valkey goes down we fail open and stop limiting which isn't good enough for our platform. As an intern, I built per-pod in-memory top-k buffers so we keep rate limiting even with the backing store gone.