API Core Overview
High-level overview of the API topology intersecting Next.js Server Actions and PostgREST endpoints.
API Reference (D)
EshtriAppN fundamentally pivots away from traditional highly coupled REST architectures. Instead, we harness a hybrid approach utilizing Supabase PostgREST for direct data manipulation paired heavily with Next.js Server Actions for complex boundary mutations.
Topology Rules
The entire backend is built on two primary consumption channels:
-
Direct RPC / PostgREST (High-Throughput) Direct instantiation of SQL commands translated natively into HTTP JSON by Supabase. Evaluated locally on the Edge browser client.
-
Next.js Edge Proxies (High-Compute / Integrations) Any integrations connecting to external systems (e.g. Stripe, AWS, internal secure cron-jobs) execute privately behind the Next.js
src/app/apiwalls. This strictly hides arbitrary keys from the public domain.
Request Execution
[!NOTE]
All client<form>actions actively utilize React 19useActionStateanduseFormStatushooks connecting directly into Server Actions seamlessly traversing the@repo/databasephysical boundary without executing client-side fetches.