From 5 Seconds to 50ms: How I Stopped Nuking My Database Every Time I Deleted an Order

My Dessert Shop Dashboard Was Choking on Its Own Data — Here's the Architecture That Fixed It Next.js App Router · Supabase · PostgreSQL performance · Incremental rollup tables The Scene: A Dashboard Loading Like It's On Dial-Up Picture this: your admin dashboard is open. You want to check last week's sales. You click the date range. Nothing. Then a spinner. A long, existential spinner. Five seconds later — if you're lucky — the numbers appear. Meanwhile, your database connection pool is gasping for air, your serverless function has basically taken a lunch break, and somewhere a Postgres row lock is just vibing, holding everything hostage. That was the state of the analytics dashboard I built for a retail franchise kiosk system on Next.js App Router + Supabase. High-volume orders, complex JSON-stored item data, coupons, loyalty coins, packaging options — and every time the admin so much as glanced at the dashboard, the server started sweating.