Designing Supabase Edge Functions
summary
Supabase Edge Functions run user code globally with Deno Deploy as the runtime, deployed to 29 regions and claiming zero millisecond startup while scaling to zero. Functions use Deno URL imports, receive injected Postgres and service secrets, validate JWTs that map to Postgres row‑level security, and recommend pgBouncer for DB connections. Architecture uses a global relay, metadata store and function store to avoid cold starts. Local CLI supports incremental rebuilds; planned features include cron scheduling, WebAssembly binaries and finer permission controls.
AI-written summary · about
chapters (12)
- 0:00Supabase Edge Functions intro
- 1:28Supabase platform overview
- 3:36Choosing Deno runtime
- 6:26Global deployment strategies
- 8:16Functions vs containers
- 9:41Deno Deploy capabilities
- 10:23Writing Edge Function
- 13:36Local dev workflow
- 14:40Monitoring in dashboard
- 15:43Client library integration
- 16:26Minimizing cold starts
- 17:51Future plans
related talks
18mBuilding Supabase Storage. DevX, performance, security - choose three
43mBeyond Serverless: How Feature-Focused Platforms Streamline Your DX
17mA new trend for databases: Platforms
52mThe trouble with extensions
47mMy entire stack is in my Postgres DB and a few power tools for my backend
18mServerless Best Practices
24m[Eng Sub]Deno: Next Generation JavaScript Runtime
56mEnabling continuous deployment with stealth, security, & smooth moves in mind