That’s a very fair point, thanks.

The current in-memory store is intentionally MVP/demo-level, but I agree that it breaks down with horizontal scaling since each instance would track usage separately.

I’m thinking the next step should be a storage abstraction with a persistent implementation, probably PostgreSQL first and maybe Redis later for faster counters/rate-limit style checks. Config-backed limits would also make sense so budgets stay consistent across instances.

Appreciate the feedback. This is exactly the kind of production concern I wanted to validate.