Distributed Social Network
11 Go services over gRPC and Redpanda, with a transactional outbox, a CQRS feed and a ClickHouse event store. OpenTelemetry, Tempo, Loki and Prometheus for observability; deployed to Kubernetes with Helm and Argo CD.
- Go
- Microservices
- Kafka
- CQRS
- PostgreSQL
- ClickHouse
- Kubernetes
- 01 Problem
- Posts, comments and likes have to reach feeds, notifications and search without a shared database or distributed transactions, and survive broker redelivery and poison messages.
- 02 Architecture
- Each service owns its store. Writes commit the row and an outbox event together; a relay publishes to Redpanda, where feed, notification, search and event-writer consumers fan out independently.
- 03 Result
- No dual writes: an event is published only if its row committed
- Idempotent consumers, so redelivery is safe
- Poison messages retry 3 times with backoff, then dead-letter
- Feeds are a CQRS read model, rebuildable from the event store
11 Go services, one event backbone
Hover a node to trace its edges. Drag to pan, Ctrl/Cmd + scroll to zoom.Tap a node to trace its edges. Pinch with two fingers to zoom.
- Edge
- Go service
- Streaming
- Data store
- Platform







