Architecture: how Tracabit processes events
Alex Rivera
Principal Systems Engineer
Sub-5ms ingestion is achieved through Bun HTTP runtime, edge TLS termination, and asynchronous batch insertions.
A detailed architectural walkthrough of our edge ingestion pipeline: TLS 1.3 termination at edge POPs, CORS origin validation, non-reversible djb2 session hashing, and asynchronous batch insertion into ClickHouse columnar storage.
By processing IP extraction and Geo-IP resolution entirely in edge memory, zero raw IP addresses ever hit persistent disk storage.
The result is sub-5ms analytical execution across billions of events with 100% compliance with global privacy regulations.
Written by Alex Rivera
Published on July 15, 2026 in Performance
Related Technical Articles
Continue reading deep dives into telemetry and privacy engineering.
Why zero-cookie analytics is the right default
Why consent banners degrade conversion by 28% and why anonymous mathematical minimization solves compliance permanently.
How to instrument a product without slowing it down
Legacy SDKs bundle 60KB+ of bloat. How we shrunk client telemetry to 1.8KB with non-blocking navigator.sendBeacon.
What agents need from your analytics API
Why LLM agents struggle with bloated JSON payloads and how structured Model Context Protocol (MCP) schemas bridge the gap.
Subscribe to our engineering journal.
Get technical teardowns, release announcements, and privacy engineering articles delivered once a month. No spam, ever.