01 / Context
The problem.
Real-time communication platforms require extreme concurrency, minimal message latency, and cryptographic security guarantees without relying exclusively on centralized relay infrastructure.
02 / My contribution
What I built.
I designed and developed a hybrid architecture combining direct P2P connections with fallback client-server relay. Implemented end-to-end encryption protocols, gRPC/WebSocket streaming handlers, and high-performance in-memory caching using Dragonfly alongside PostgreSQL persistence.
03 / Approach
Engineering decisions.
Adopt Go for backend concurrency
Lightweight goroutines handle tens of thousands of simultaneous persistent socket connections with negligible memory overhead.
Accelerate with Dragonfly in-memory cache
Multi-threaded in-memory caching reduced session state lookup latency to sub-millisecond speeds under heavy message floods.
Cross-platform parity with Flutter & Tauri
Built native cross-platform clients ensuring identical cryptographic and networking behavior across mobile and desktop environments.
Resilient hybrid fallback
Direct P2P communication is preferred when NAT traversal succeeds, gracefully falling back to encrypted relay without interrupting the user experience.
04 / Outcome & context
What this work shows.
Engineered an operational messaging engine capable of high message throughput with end-to-end encrypted payload delivery and low latency.
Secure systems balance cryptographic integrity, network protocol design, and concurrency primitives.
Operational project / The cover is a concept illustration. This case study focuses on my engineering contribution and system-level architecture.