supabase-fallback

Query Supabase directly using PostgREST REST endpoints at /rest/v1 with environment variables for URL and API keys. Use Anon keys for read-only access or Service Role keys for write operations on tables like site_config_kv, bypassing the backend entirely when it's unavailable.

Yes, Supabase REST API supports SELECT, INSERT, UPDATE, DELETE, and UPSERT operations through PostgREST endpoints. Use Service Role keys to enable write access; Anon keys restrict to read-only, enforcing permission boundaries for different client types.

Anon keys provide read-only access for public, browser-based clients; Service Role keys enable full write capabilities (INSERT, UPDATE, DELETE) for server-side or trusted clients. Choose based on your security requirements and whether the client needs data modification permissions.

Set environment variables for your Supabase URL and API keys, then construct RESTful calls to PostgREST /rest/v1 endpoints. On-premises Supabase instances expose the same REST interface, allowing direct queries when configured with proper URL and authentication credentials.

Implement fallback Supabase queries when your Spring Boot backend may be offline or unavailable but you need continued data access. This pattern ensures operational resilience in on-premises environments where backend downtime would otherwise block all database operations.

PostgREST REST API works with any Supabase table; common use cases include site_config_kv for configuration data. Supported operations are SELECT, INSERT, UPDATE, DELETE, and UPSERT, each callable as standard HTTP methods against /rest/v1 endpoints for your target tables.