Files

T

Ilia Denisov 118f7c17a2 phase 4: connectrpc on the gateway authenticated edge

Replace the native-gRPC server bootstrap with a single
`connectrpc.com/connect` HTTP/h2c listener. Connect-Go natively
serves Connect, gRPC, and gRPC-Web on the same port, so browsers can
now reach the authenticated surface without giving up the gRPC
framing native and desktop clients may use later. The decorator
stack (envelope → session → payload-hash → signature →
freshness/replay → rate-limit → routing/push) is reused unchanged
behind a small Connect → gRPC adapter and a `grpc.ServerStream`
shim around `*connect.ServerStream`.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

2026-05-07 11:49:28 +02:00

examples.md

feat: notification service

2026-04-22 08:49:45 +02:00

flows.md

phase 4: connectrpc on the gateway authenticated edge

2026-05-07 11:49:28 +02:00

README.md

feat: edge gateway service

2026-04-02 19:18:42 +02:00

redis-config.md

feat: backend service

2026-05-06 10:14:55 +03:00

runbook.md

phase 4: connectrpc on the gateway authenticated edge

2026-05-07 11:49:28 +02:00

runtime.md

phase 4: connectrpc on the gateway authenticated edge

2026-05-07 11:49:28 +02:00

README.md

Edge Gateway Docs

This directory keeps service-local documentation that is too detailed for the root architecture documents and too diagram-heavy for the module README.

Sections:

Primary references:

../README.md for service scope, contracts, configuration, and operational behavior
../openapi.yaml for the public REST contract
../../README.md for workspace-level architecture
../../SECURITY.md for the transport security model