SQL from the Frontend: Viable or Not?

on YouTube ↗45m

" summary

Claim: exposing SQL to the client massively speeds early development but is not production-ready alone. Demonstrated tools and patterns: Neon Author, Postgres RLS protecting per-row access (RLS shipped 2016), PostgREST/Supabase-style proxies, and Drizzle-generated policies. Built examples: todo app and a Twitter/X-style chat with RLS rules that work for reads/writes but leave secrets and third‑party API calls unresolved. Operational gaps: need robust rate limiting, a query allowlist, and avoidance of large stored‑procedure business logic.

AI-written summary · about

" chapters (11)

1. 0:00Introduction
2. 1:54Frontend SQL architecture
3. 4:50Traditional backend roles
4. 10:12Can DBs replace backend logic
5. 15:50PostgreSQL RLS explained
6. 18:44Social network modeling with RLS
7. 24:47PostgREST and Neon Auth
8. 28:50Remaining challenges
9. 31:02Hybrid architecture future
10. 33:49Summary and future
11. 34:58Q&A

" related talks

• 29mApps, Stacks, and Frameworks: Avoiding “Shiny Object” SyndromeAngel Rivera · PHP UK Conference 2020
• 31mWriting an interactive streaming SQL engine and pre-parser using FlinkKenny Gorman · Flink Forward Europe 2019
• 15mReactifying your applicationKristof Van Sever · Devoxx Belgium 2017
• 28mPanel Discussion: The GraphQL Production RoundtableJory Burson, Stephen Spalding, Clarice Abreu, Aileen Chen · GraphQLConf 2026
• 36mKnowing What You See - Let's Talk About Front-end ConsistencyYifan Wu · Strange Loop 2016
• 31mReimagining the frontend-backend divide thanks to GraphQLUri Goldshtein · ngVikings 2019
• 51mBuilding a Realtime "Backend in a Box" with PostgreSQL and VueRob Conery · NDC Sydney 2019
• 03mGraphQL Revolutionizing API DevelopmentJitendra Kumar · PGConf India 2025