Solo SaaS6 min
Synchronizing one moment across every screen
Devices disagree about the time. How to fire one event at once on hundreds of screens worldwide, with a server clock, offset estimation and a scheduled reveal.
Notes / Solo SaaS
Engineering a SaaS alone
Running a product alone removes the gap between writing code and being responsible for it. These notes are the incidents and the design decisions from three products I built, shipped and still operate on my own, including the ones that went badly.
Covered here
- Incidents
- Real-time synchronization
- Sandboxed execution
- Quotas and limits
- Webhooks
- Operating solo
3 notes
Solo SaaS7 min
Running untrusted code in 14 languages without losing the host
Running candidate code for real means running hostile code on your own servers. The threat model, the limits that matter, and what a container won't give you.
Solo SaaS5 min
The free-tier quota that took my product down for two days
A daily read quota reset at 07:00 UTC, a poller that never slept, and a product that died every afternoon. What went wrong and the three things that hid it.