feat(rate-limiting): Implement core rate limiting functionality with configuration, decision-making, metrics, middleware, and service registration
- Add RateLimitConfig for configuration management with YAML binding support. - Introduce RateLimitDecision to encapsulate the result of rate limit checks. - Implement RateLimitMetrics for OpenTelemetry metrics tracking. - Create RateLimitMiddleware for enforcing rate limits on incoming requests. - Develop RateLimitService to orchestrate instance and environment rate limit checks. - Add RateLimitServiceCollectionExtensions for dependency injection registration.
This commit is contained in:
@@ -23,9 +23,9 @@ Last updated: 2025-11-25
|
||||
4) Results are persisted append-only; WebSocket pushes status to clients.
|
||||
|
||||
## Storage & queues
|
||||
- Mongo stores DAG specs, versions, and run history (per-tenant collections or tenant key prefix).
|
||||
- Queues: Redis/Mongo-backed FIFO per tenant; message includes `traceparent`, `runToken`, `dagVersion`, `inputsHash`.
|
||||
- Artifacts (logs, outputs) referenced by content hash; stored in object storage or Mongo GridFS; hashes recorded in run record.
|
||||
- PostgreSQL stores DAG specs, versions, and run history (per-tenant tables or tenant key prefix).
|
||||
- Queues: Redis/PostgreSQL-backed FIFO per tenant; message includes `traceparent`, `runToken`, `dagVersion`, `inputsHash`.
|
||||
- Artifacts (logs, outputs) referenced by content hash; stored in object storage or PostgreSQL large objects; hashes recorded in run record.
|
||||
|
||||
## Security & AOC alignment
|
||||
- Mandatory `X-Stella-Tenant`; cross-tenant DAGs prohibited.
|
||||
|
||||
Reference in New Issue
Block a user