Engineering decision logs, database schemas, and operational notes.

Public build notes & architecture logs.

We build and operate our own software products daily. These notes document genuine technical choices, performance trade-offs, and architecture decisions from real production systems.

RSS Feed available for technical founders and developers.
Subscribe via RSS ↗
Chronological Log

Decisions & Post-Mortems

01

Why we picked PostgreSQL/PostGIS over MongoDB Geospatial for fleet waypoint audit trails

2026-10-04 • Fleet Operations Platform • Database Engineering

When tracking thousands of GPS pings across unpredictable transit routes, geofencing queries require deterministic query execution plans. We evaluated MongoDB 2dsphere indexes versus PostgreSQL with PostGIS GiST R-Tree indexing. PostGIS delivered predictable sub-millisecond containment verification and strict ACID guarantees for regulatory driver logs without document locking contention.

PostGIS PostgreSQL Redis Streams Geofencing
02

Zero-network UI transitions: SQLite in WASM vs client-side IndexedDB

2026-09-28 • Link Organiser • Client Performance

Standard IndexedDB key-value queries slow down when users perform multi-attribute fuzzy searches across tens of thousands of developer links. For Link Organiser, we compiled SQLite to WebAssembly running inside a Dedicated Web Worker. Search queries execute locally in under 3 milliseconds across 50,000 bookmarks with zero server roundtrips, followed by background delta syncing.

SQLite WASM Web Workers Offline-First Next.js
03

Edge caching architecture for real-time developer tool discovery

2026-09-15 • UtilityHub • Cloud Infrastructure

UtilityHub surfaces trending repositories, AI skills, and developer ecosystem resources. Rather than querying origin databases on every request, we compile static catalog manifests pushed to Cloudflare Pages edge nodes with stale-while-revalidate headers. Global TTFB stays minimal and origin infrastructure costs remain virtually zero under viral traffic spikes.

Cloudflare Pages Astro Edge Caching Algolia Search
04

Designing WhatsApp webhook resilience during clinic rush hours

2026-08-30 • Healthcare Blueprint • Automation & Queues

In healthcare appointment workflows, 80% of patient inquiries hit reception systems between 8:00 AM and 10:00 AM. Synchronous HTTP webhook handlers frequently time out under Meta's 15-second cutoff window. We implemented an asynchronous Redis BullMQ ingestion layer with idempotent message hashing, ensuring zero duplicate bookings and instant 200 OK acknowledgments to Meta's servers.

WhatsApp Business API BullMQ Redis Idempotency

Have an architectural or automation challenge?

Tell us about your system bottlenecks and technical goals. We'll outline practical engineering approaches.

Request a free audit ↗