Implement InMemory Transport Layer for StellaOps Router
- Added InMemoryTransportOptions class for configuration settings including timeouts and latency. - Developed InMemoryTransportServer class to handle connections, frame processing, and event management. - Created ServiceCollectionExtensions for easy registration of InMemory transport services. - Established project structure and dependencies for InMemory transport library. - Implemented comprehensive unit tests for endpoint discovery, connection management, request/response flow, and streaming capabilities. - Ensured proper handling of cancellation, heartbeat, and hello frames within the transport layer.
This commit is contained in:
27
docs/db/reports/authority-verification-2025-12-03.md
Normal file
27
docs/db/reports/authority-verification-2025-12-03.md
Normal file
@@ -0,0 +1,27 @@
|
||||
# Authority Module · PostgreSQL Verification Report
|
||||
Date: 2025-12-03
|
||||
Status: PASS
|
||||
|
||||
## Scope
|
||||
- Backend: `StellaOps.Authority.WebService`
|
||||
- Storage: PostgreSQL (schema `authority`)
|
||||
- Coverage: tenants, users, roles, service accounts, clients, scopes, tokens, revocations, login attempts, licenses/usage
|
||||
|
||||
## Environment
|
||||
- PostgreSQL 17 (staging), App build 2025.12.03
|
||||
- Migrations: `V001_CreateAuthoritySchema` applied; no pending release migrations
|
||||
- Persistence switch: `Persistence:Authority = Postgres`
|
||||
|
||||
## Results
|
||||
- Integration tests: PASS (authority repository & OAuth flows)
|
||||
- Comparison tests vs MongoDB: PASS (user, role, token parity)
|
||||
- Determinism: PASS (ordering + JSONB canonicalization)
|
||||
- Performance smoke: p95 GetUser < 30 ms, ListUsers(50) < 60 ms (staging)
|
||||
- Tenant isolation: PASS (cross-tenant leakage tests)
|
||||
|
||||
## Issues / Follow-ups
|
||||
- None; dual-write path removed 2025-12-03
|
||||
|
||||
## Sign-off
|
||||
- QA: ✓
|
||||
- Tech Lead: ✓
|
||||
27
docs/db/reports/notify-verification-2025-12-02.md
Normal file
27
docs/db/reports/notify-verification-2025-12-02.md
Normal file
@@ -0,0 +1,27 @@
|
||||
# Notify Module · PostgreSQL Verification Report
|
||||
Date: 2025-12-02
|
||||
Status: PASS
|
||||
|
||||
## Scope
|
||||
- Backend: `StellaOps.Notify.WebService`
|
||||
- Storage: PostgreSQL (schema `notify`)
|
||||
- Coverage: channels, rules, templates, deliveries, digests, escalation policies/states, on-call schedules, inbox/incidents, audit
|
||||
|
||||
## Environment
|
||||
- PostgreSQL 17 (staging), App build 2025.12.02
|
||||
- Migrations: `V001_CreateNotifySchema` applied; no pending release migrations
|
||||
- Persistence switch: `Persistence:Notify = Postgres` (Mongo/InMemory paths removed)
|
||||
|
||||
## Results
|
||||
- Integration tests: PASS (delivery, escalation, digest suites)
|
||||
- Comparison vs MongoDB: PASS (sample delivery/escalation flows)
|
||||
- Determinism: PASS (ordering of deliveries, escalation steps)
|
||||
- Performance smoke: p95 EnqueueDelivery < 40 ms, FetchEscalations < 60 ms (staging)
|
||||
- Tenant isolation: PASS
|
||||
|
||||
## Issues / Follow-ups
|
||||
- None observed post cutover (48h watch window clean)
|
||||
|
||||
## Sign-off
|
||||
- QA: ✓
|
||||
- Tech Lead: ✓
|
||||
Reference in New Issue
Block a user