Skip to content

Key-value based rate limiting #5545

@jprenken

Description

@jprenken

MySQL-compatible databases are inefficient for some of Boulder's most demanding data storage needs:

  • OCSP responses are perfect for a simpler and more performant key-value data model.
  • Rate limit data (a broad category) is ephemeral, and requires no ACID guarantees.

In order for Boulder to support large and growing environments, it would be nice for it to support Redis as a storage backend for these purposes. For OCSP responses, there will need to be some ability to insert/update data in both MySQL and Redis in parallel (e.g. during a transition).

---- (project tracking added by @beautifulentropy) ----

Metadata

Metadata

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions