Define MySQL schema for tenants, API keys, and aggregate usage counters #22

New issue

Closed

opened 2026-07-01 00:58:06 +00:00 by manlycucumber · 1 comment

manlycucumber commented

2026-07-01 00:58:06 +00:00

(Migrated from github.com)

Problem

MySQL must store only API keys, tenants, and aggregate usage counters — never a row per request. The schema needs to support issuing keys, scoping them to tenants, and metering usage in aggregate buckets.

Acceptance criteria

Schema defines tenants, API keys (hashed), and aggregate usage counters keyed by time bucket.
No table records individual request rows.
Migrations create and roll back the schema cleanly.
The schema is documented with the privacy rationale.

Notes

Privacy-first: store hashed keys and aggregate counts only, never per-request logs.

## Problem MySQL must store only API keys, tenants, and aggregate usage counters — never a row per request. The schema needs to support issuing keys, scoping them to tenants, and metering usage in aggregate buckets. ## Acceptance criteria - [ ] Schema defines tenants, API keys (hashed), and aggregate usage counters keyed by time bucket. - [ ] No table records individual request rows. - [ ] Migrations create and roll back the schema cleanly. - [ ] The schema is documented with the privacy rationale. ## Notes Privacy-first: store hashed keys and aggregate counts only, never per-request logs.

manlycucumber commented

2026-07-03 06:10:59 +00:00

(Migrated from github.com)

Delivered in #137 (squash-merged to develop).

Delivered in #137 (squash-merged to `develop`).

manlycucumber referenced this issue from a commit

2026-08-05 19:02:25 +00:00

feat: API keys, per-tenant quotas, and per-key rate limits (#137)

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

Directorium/Api#22

No description provided.

Rows
Columns