SysPad › Examples › Community app on Supabase
Community app on Supabase
A community platform on Supabase (Postgres + Auth + Realtime as one plan-priced backend), with Redis Cloud for session/rate-limit checks and direct SES for transactional email.
Plan-priced compute (not per-operation billing) as the throughput ceiling, and a direct-to-SES email choice made on cost rather than convenience.
- Throughput: 4,000 req/sec
- First to saturate: Nothing at this load
- Estimated cost: $32k/mo
How it works
- Supabase
- Postgres, Auth and Realtime as one plan-priced backend. Because the price is a plan rather than a per-operation meter, growth shows up as a throughput ceiling long before it shows up on the invoice.
- Redis Cloud
- Session and rate-limit checks, kept off Postgres. They are high-frequency and short-lived, exactly the work you do not want competing with real queries for connections.
- Transactional Email
- Sent at AWS rates instead of through an email platform, a deliberate cost choice for a backend feature. The send-rate quota, not the price, is what bites first during a signup spike.