Decisions
Technical and architectural decisions from real projects. Each entry documents the context, alternatives, and why a particular path was chosen.
3 decisions documented
Room abstraction over NATS JetStream for game backends Designing Pulse — the backend layer for an unannounced tycoon sim. Needed session semantics, pub/sub messaging, and a path to multiplayer without standing up bespoke game-server in... Read decision NATS JetStream over Kafka for event ingestion Building a distributed analytics and feature-flag backend for a SaaS client. Multiple Golang services needed to publish events reliably. The team was small and already used NATS fo... Read decision Vulkan plus in-process WebRTC for desktop screen sharing A client needed native Mac and Windows apps with real-time screen sharing. Electron was too heavy; the rendering path needed GPU access. WebRTC was the transport layer of choice fo... Read decision