Posts about architecture
One suite or a separate tool for each job: the trade-offs
Shared login, one database and one search, or specialized products that go deeper. What zerosoft's apps share today, what they don't, and when to pick specialists.
Versioned migrations without an ORM: a baseline, a list and one table
How zerosoft changes its SQLite/libSQL schema with numbered migrations in plain TypeScript, why each one must survive running twice at once, and the SQLite trap that can delete data.
Rate limiting without Redis: one table and one UPSERT
How zerosoft rate-limits its API and public endpoints with a fixed-window counter in the same SQLite/libSQL database, and when that stops being a good idea.
How Cal handles time zones: wall clocks, UTC and DST
What Cal stores in UTC, what it keeps as wall-clock time, how slots survive DST changes, and how emails and .ics invites reach the guest in their own time zone.
How Link is built: Next.js, SQLite and one route handler
The redirect is a route handler that answers in milliseconds, backed by SQLite and nothing else. The whole architecture, on one page.
SQLite is enough for apps like ours
The most deployed database runs in your phone, your browser and Link. Millions of rows, WAL mode, and backups that are a file copy.