Initializing System StateSUB-100MS EDGE SLA // INGRESS ROUTING
AI workflows, event pipelines, and product systems shaped by real constraints: where a request can fail, what must be retried, and which state has to stay correct.
System focus
I work on the failure boundaries beneath an interface: incoming requests, deferred work, and the state a system cannot afford to lose.
Real-time event streaming platform that routes application events such as signups, payments, and errors directly to Discord channels.
Why did this project exist? Early-stage SaaS teams often resort to Slack or Discord webhooks for system alerts. But direct webhook calls from client code create three immediate hazards: plaintext webhook URL leakage, blocking synchronous HTTP round-trips on user-facing endpoints, and uncontrolled alert spam during error loops. PingPanda decouples the application from destination webhooks through an authenticated, rate-limited edge ingress gateway.
We rejected a traditional monolithic Express server and synchronous PostgreSQL write pipeline because relational connection pools stall under webhook retry storms. Instead, PingPanda separates ingress acknowledgement from database persistence using a 3-tier edge-to-storage topology: (1) Edge Ingress Gateway (Hono.js on Edge) intercepts HTTP POST payloads, validates HMAC-SHA256 signatures via Web Crypto API, and verifies tenant API keys in ~12ms without touching Node.js polyfills; (2) Atomic Quota & Storage Engine (PostgreSQL 16 + Prisma) executes a single-statement atomic increment transaction that simultaneously validates billing tier headroom and persists event metadata; (3) Async Alert Dispatcher (QStash + Discord Webhooks) formats rich embedded Discord alert cards and dispatches notifications asynchronously, isolating upstream client response times from Discord API rate limits.
Why Hono.js over Express at the Edge: Express requires polyfilling Node.js http stream objects, adding 220ms of cold-start latency and 72% bundle bloat on serverless workers. Hono operates directly on native Web Standard Request and Response streams, executing signature validation in 12ms
Real-time event streaming with sub-second latency to Discord channels. Stripe-powered subscription tiers enforce category limits automatically.