Supabase architecture (Postgres, Auth, Storage, Realtime, Edge Functions) - Step-by-Step Execution

Process Flow - Supabase architecture (Postgres, Auth, Storage, Realtime, Edge Functions)

Client Request

↓

Auth Service

↓

Postgres Database

↓

Realtime Server

↓

Storage Service

↓

Edge Functions

↓

Response to Client

Client sends request which first goes to Auth for verification, then interacts with Postgres. Postgres connects to Realtime, Storage, and Edge Functions to handle data, live updates, files, and custom logic.

Execution Sample

Supabase

1. Client sends login request
2. Auth verifies credentials
3. On success, client queries Postgres
4. Postgres triggers Realtime updates
5. Client uploads file to Storage
6. Edge Functions run custom logic

This flow shows how a client interacts with Supabase services step-by-step.

Process Table

Step	Action	Service Involved	State Change	Client Impact
1	Client sends login request	Client -> Auth	Auth receives credentials	Waiting for auth result
2	Auth verifies credentials	Auth	User authenticated or rejected	Receives auth token if success
3	Client queries database	Client -> Postgres	Postgres processes query	Receives requested data
4	Postgres triggers realtime update	Postgres -> Realtime	Realtime broadcasts changes	Client UI updates live
5	Client uploads file	Client -> Storage	File stored securely	File available for access
6	Edge Functions execute	Edge Functions	Custom logic runs on events	Client gets processed results
7	End of flow	-	-	Client interaction complete

💡 All steps complete; client has authenticated, accessed data, received live updates, stored files, and used custom logic.

Status Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	After Step 5	After Step 6	Final
Auth Token	None	Valid token or None	Valid token	Valid token	Valid token	Valid token	Valid token
Database Data	Empty	Empty	Queried data	Queried data	Queried data	Queried data	Queried data
Realtime State	Idle	Idle	Idle	Broadcasting updates	Broadcasting updates	Broadcasting updates	Broadcasting updates
Storage Files	Empty	Empty	Empty	Empty	File stored	File stored	File stored
Edge Function Result	None	None	None	None	None	Processed result	Processed result

Key Moments - 3 Insights

Why does the client need to authenticate before accessing the database?

Authentication ensures only authorized users can query the database, as shown in step 2 of the execution_table where Auth verifies credentials before Postgres processes queries in step 3.

How does realtime update the client interface?

Postgres triggers Realtime to broadcast changes (step 4), which updates the client UI live without needing manual refresh, as seen in the 'Client Impact' column.

What role do Edge Functions play in this architecture?

Edge Functions run custom logic on events (step 6), allowing the client to get processed results beyond simple database queries, enhancing flexibility.

Visual Quiz - 3 Questions

Look at the execution_table, what service verifies user credentials?

A Postgres Database

B Realtime Server

C Auth Service

D Storage Service

💡 Hint

Check step 2 in the execution_table where authentication happens.

At which step does the client receive live updates?

A Step 3

B Step 4

C Step 5

D Step 6

💡 Hint

Look at the 'Client Impact' column for live UI updates in the execution_table.

If the client skips authentication, what happens to the database query step?

A Database query is rejected or blocked

B Realtime broadcasts updates anyway

C Postgres processes query normally

D Edge Functions run without data

💡 Hint

Refer to the key_moments about why authentication is needed before database access.

Concept Snapshot

Supabase architecture includes:
- Auth for user verification
- Postgres as the main database
- Realtime for live data updates
- Storage for file management
- Edge Functions for custom backend logic
Client requests flow through Auth, then Postgres, triggering Realtime, Storage, and Edge Functions as needed.

Full Transcript

Supabase architecture works by first having the client send a request that goes to the Auth service to verify the user. Once authenticated, the client can query the Postgres database. Postgres can trigger Realtime to send live updates to the client interface. Clients can upload files to Storage, which securely stores them. Edge Functions run custom backend logic on events to extend functionality. This flow ensures secure, real-time, and flexible cloud services for applications.