How Scrollr
works.
From source API to your desktop in milliseconds. A decoupled, CDC-driven pipeline built on Go, Rust, React, and Redis.
The pipeline
Four stages from data source to your screen
Data Sources
TwelveData WebSocket for market data, api-sports.io for scores, RSS/Atom feeds for news.
Ingestion Services
Three independent Rust services collect, normalize, and write data to PostgreSQL. Each runs its own schedule and connection strategy.
PostgreSQL + CDC
All data lands in PostgreSQL. Sequin monitors table changes via CDC (Change Data Capture) and fires webhooks to the core API.
Real-time Delivery
Core API maps each CDC record to a topic in-process and publishes via Redis pub/sub. Every replica fans out to its own SSE clients.
CDC record flow
How a single data change reaches the right user
Rust Service
Writes to PostgreSQL
Sequin CDC
Detects row changes
Core API
POST /webhooks/sequin
Topic Router
record → cdc:{source}:{key}
Redis Pub/Sub
events:user:{sub}
SSE → Client
Desktop App
Design principles
The rules that shape every architectural decision
Tech stack
What powers each layer
Core API
Go 1.25
Fiber v2, pgx, Redis
SSE Hub
Per-user Redis Pub/Sub channels
Logto
Self-hosted OIDC, JWT validation
Ingestion
Rust
tokio async runtime
WebSocket
TwelveData persistent connection
HTTP Polling
api-sports.io, RSS 5min
Frontend
React 19
Vite 7, TanStack Router
Tailwind v4
daisyUI theme system
Motion
Production-grade animations
Desktop
Tauri v2
Cross-platform native shell
React 19
Multi-window UI
SSE + Polling
Real-time data delivery
Infrastructure
PostgreSQL
Shared DB, natural table isolation
Redis
Cache, Pub/Sub, registration
Sequin
CDC webhooks from PostgreSQL
Deployment
Kubernetes
DigitalOcean DOKS + DOCR
GitHub Actions
Build, deploy, smoke test
nginx + cert-manager
Ingress, TLS
