Supabase Reference Architecture

Overview

Production-ready architecture patterns for Supabase integrations.

Prerequisites

• Understanding of layered architecture
• Supabase SDK knowledge
• TypeScript project setup
• Testing framework configured

Project Structure

my-supabase-project/
├── src/
│   ├── supabase/
│   │   ├── client.ts           # Singleton client wrapper
│   │   ├── config.ts           # Environment configuration
│   │   ├── types.ts            # TypeScript types
│   │   ├── errors.ts           # Custom error classes
│   │   └── handlers/
│   │       ├── webhooks.ts     # Webhook handlers
│   │       └── events.ts       # Event processing
│   ├── services/
│   │   └── supabase/
│   │       ├── index.ts        # Service facade
│   │       ├── sync.ts         # Data synchronization
│   │       └── cache.ts        # Caching layer
│   ├── api/
│   │   └── supabase/
│   │       └── webhook.ts      # Webhook endpoint
│   └── jobs/
│       └── supabase/
│           └── sync.ts         # Background sync job
├── tests/
│   ├── unit/
│   │   └── supabase/
│   └── integration/
│       └── supabase/
├── config/
│   ├── supabase.development.json
│   ├── supabase.staging.json
│   └── supabase.production.json
└── docs/
    └── supabase/
        ├── SETUP.md
        └── RUNBOOK.md

Layer Architecture

┌─────────────────────────────────────────┐
│             API Layer                    │
│   (Controllers, Routes, Webhooks)        │
├─────────────────────────────────────────┤
│           Service Layer                  │
│  (Business Logic, Orchestration)         │
├─────────────────────────────────────────┤
│          Supabase Layer        │
│   (Client, Types, Error Handling)        │
├─────────────────────────────────────────┤
│         Infrastructure Layer             │
│    (Cache, Queue, Monitoring)            │
└─────────────────────────────────────────┘

Key Components

Step 1: Client Wrapper

// src/supabase/client.ts
export class SupabaseService {
  private client: SupabaseClient;
  private cache: Cache;
  private monitor: Monitor;

  constructor(config: SupabaseConfig) {
    this.client = new SupabaseClient(config);
    this.cache = new Cache(config.cacheOptions);
    this.monitor = new Monitor('supabase');
  }

  async get(id: string): Promise<Resource> {
    return this.cache.getOrFetch(id, () =>
      this.monitor.track('get', () => this.client.get(id))
    );
  }
}

Step 2: Error Boundary

// src/supabase/errors.ts
export class SupabaseServiceError extends Error {
  constructor(
    message: string,
    public readonly code: string,
    public readonly retryable: boolean,
    public readonly originalError?: Error
  ) {
    super(message);
    this.name = 'SupabaseServiceError';
  }
}

export function wrapSupabaseError(error: unknown): SupabaseServiceError {
  // Transform SDK errors to application errors
}

Step 3: Health Check

// src/supabase/health.ts
export async function checkSupabaseHealth(): Promise<HealthStatus> {
  try {
    const start = Date.now();
    await supabaseClient.ping();
    return {
      status: 'healthy',
      latencyMs: Date.now() - start,
    };
  } catch (error) {
    return { status: 'unhealthy', error: error.message };
  }
}

Data Flow Diagram

User Request
     │
     ▼
┌─────────────┐
│   API       │
│   Gateway   │
└──────┬──────┘
       │
       ▼
┌─────────────┐    ┌─────────────┐
│   Service   │───▶│   Cache     │
│   Layer     │    │   (Redis)   │
└──────┬──────┘    └─────────────┘
       │
       ▼
┌─────────────┐
│ Supabase    │
│   Client    │
└──────┬──────┘
       │
       ▼
┌─────────────┐
│ Supabase    │
│   API       │
└─────────────┘

Configuration Management

// config/supabase.ts
export interface SupabaseConfig {
  apiKey: string;
  environment: 'development' | 'staging' | 'production';
  timeout: number;
  retries: number;
  cache: {
    enabled: boolean;
    ttlSeconds: number;
  };
}

export function loadSupabaseConfig(): SupabaseConfig {
  const env = process.env.NODE_ENV || 'development';
  return require(`./supabase.${env}.json`);
}

Instructions

Step 1: Create Directory Structure

Set up the project layout following the reference structure above.

Step 2: Implement Client Wrapper

Create the singleton client with caching and monitoring.

Step 3: Add Error Handling

Implement custom error classes for Supabase operations.

Step 4: Configure Health Checks

Add health check endpoint for Supabase connectivity.

Output

• Structured project layout
• Client wrapper with caching
• Error boundary implemented
• Health checks configured

Error Handling

Issue	Cause	Solution
Circular dependencies	Wrong layering	Separate concerns by layer
Config not loading	Wrong paths	Verify config file locations
Type errors	Missing types	Add Supabase types
Test isolation	Shared state	Use dependency injection

Examples

Quick Setup Script

# Create reference structure
mkdir -p src/supabase/{handlers} src/services/supabase src/api/supabase
touch src/supabase/{client,config,types,errors}.ts
touch src/services/supabase/{index,sync,cache}.ts

Resources

• Supabase SDK Documentation
• Supabase Best Practices

Flagship Skills

For multi-environment setup, see supabase-multi-env-setup.