Opening high traffic access points using Go
summary
Built a full member system for ~1,000 users using a Go monolith API that writes a single-authoritative SQLite file, synced to an edge device with Turso sync every 30s. A mini PC inside the turnstile reads QR scans as keyboard input, validates against the SQLite on the edge, and sends opens via RS485 serial commands to the hardware. Deployed with Fly.io, mobile app via Expo/React Native, logging to local files and Discord; it runs reliably offline and costs under ~$5/month (setup ≈ $700).
AI-written summary · about
chapters (24)
- 0:00Introduction
- 1:04Talk overview
- 3:09Project requirements
- 8:04SQLite for edge sync
- 14:45High traffic access points
- 17:13Door hardware setup
- 19:21Go door control code
- 22:11Deployment strategies
- 27:56Monitoring on a budget
- 31:27Cost breakdown
- 32:31Future possibilities
- 32:54Q&A
- 33:15Raspberry Pi vs mini PC
- 35:03Sync frequency
- 36:07Disaster recovery
- 36:51Security challenges
- 38:55Hardware risks
- 40:40Database sync patterns
- 41:45Monolith vs microservices
- 42:46Post-deployment fixes
- 44:14Fly.io vs Turso
- 45:39Design changes
- 47:02QR code security
- 49:51Closing
