stella-ops.org/git.stella-ops.org
1
0
Fork 0
Code Issues Pull Requests Actions 2 Releases Wiki Activity

semi implemented and features implemented save checkpoint

Browse Source
This commit is contained in:
master
2026-02-08 18:00:49 +02:00
parent 04360dff63
commit 1bf6bbf395
20895 changed files with 716795 additions and 64 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
docs/features/unchecked/router/router-backpressure.md Normal file
View File

@@ -0,0 +1,24 @@
# Router Backpressure (HTTP 429/503 + Retry-After)
## Module
Router
## Status
IMPLEMENTED
## Description
Rate limiting and backpressure testing with dedicated chaos test suite for the router, including Testcontainers-based fixture for burst testing.
## Implementation Details
- **Modules**: `src/Router/__Libraries/StellaOps.Router.Gateway/RateLimit/`, `src/Router/__Libraries/StellaOps.Router.Transport.InMemory/`
- **Key Classes**:
- `ValkeyRateLimitStore` (`src/Router/__Libraries/StellaOps.Router.Gateway/RateLimit/ValkeyRateLimitStore.cs`) - Valkey-backed rate limit storage for per-instance throttling
- `InMemoryRateLimiter` (`src/Router/__Libraries/StellaOps.Messaging.Transport.InMemory/InMemoryRateLimiter.cs`) - in-memory rate limiter for testing
- **Source**: Feature matrix scan
## E2E Test Plan
- [ ] Send requests exceeding the rate limit and verify HTTP 429 responses with Retry-After header
- [ ] Verify HTTP 503 response when all instances are overloaded
- [ ] Verify backpressure propagation: confirm the gateway signals backpressure to callers when queues are full
- [ ] Verify rate limit recovery: after throttling, confirm requests resume when the limit window expires
- [ ] Verify per-instance rate limiting: confirm each microservice instance has its own rate limit counter