Drivers and Backends
How Athena routes operations across PostgreSQL, Supabase, and Scylla backends.
Backend Model
Athena resolves backend execution through the selected logical client from X-Athena-Client.
Supported backend families:
- PostgreSQL via SQLx pools
- Supabase REST or RPC routing
- Scylla/Cassandra CQL driver
Backend Selection Inputs
X-Athena-Client: primary client and backend selector.x-supabase-urlandx-supabase-key: direct Supabase routing when using the Supabase path.- JDBC override headers when direct PostgreSQL routing is enabled.
Operational Notes
- Startup can soft-fail unavailable configured clients while keeping healthy pools active.
- Catalog-backed clients are loaded after config clients and can become available when connectivity is restored.
- Supabase health-aware behavior includes offline tracking and reset support.
Related APIs
POST /query/sqlPOST /gateway/sqlPOST /gateway/rpcGET /health/cluster
Reference
See Reference -> Athena API Reference -> query, gateway, rpc, and health sections.