Multi-Tenant SaaS Architecture on AWS & Laravel: Database Isolation, Subdomains & Stripe Billing

01 Multi-Tenancy Isolation Models: Column vs Schema vs Database-per-Tenant

In enterprise Software-as-a-Service (SaaS) engineering, choosing the right tenant data isolation model represents the most critical architectural decision. The three primary models each offer distinct trade-offs across cost, operational overhead, and compliance:

02 Dynamic Subdomain Resolution & Wildcard SSL on AWS

When a client signs up for your SaaS at acme.yourproduct.com, they expect immediate access without waiting for DNS propagation. By binding an AWS Application Load Balancer (ALB) to an AWS Certificate Manager (ACM) wildcard certificate (*.yourproduct.com), all incoming traffic routes straight to Laravel EC2 auto-scaling instances or AWS ECS Fargate containers.

// Laravel 11 Dynamic Tenant Bootstrapper
namespace App\Providers;
use Illuminate\Support\ServiceProvider;
use App\Models\Tenant;
use Illuminate\Support\Facades\DB;

class TenantServiceProvider extends ServiceProvider {
    public function boot(): void {
        $host = request()->getHost();
        $parts = explode('.', $host);
        
        if (count($parts) >= 3 && $parts[0] !== 'www') {
            $subdomain = $parts[0];
            $tenant = Tenant::where('subdomain', $subdomain)->where('is_active', true)->firstOrFail();
            
            config(['database.connections.tenant.database' => $tenant->database_name]);
            DB::purge('tenant');
            DB::reconnect('tenant');
            DB::setDefaultConnection('tenant');
            
            app()->instance('currentTenant', $tenant);
        }
    }
}

03 Metered Stripe Billing & Webhook Idempotency in Redis

Enterprise SaaS platforms monetize through hybrid billing: fixed recurring subscriptions plus metered consumption fees (API calls, storage, active seats). Processing Stripe webhooks requires strict signature verification and Redis transaction locking to eliminate duplicate charge events:

// Stripe Webhook Idempotent Handler in Laravel
public function handleWebhook(Request $request) {
    $payload = $request->getContent();
    $sigHeader = $request->header('Stripe-Signature');
    $event = \Stripe\Webhook::constructEvent($payload, $sigHeader, config('services.stripe.webhook_secret'));

    // Prevent duplicate webhook replay attacks using Redis lock
    $lockKey = "stripe:event:{$event->id}";
    $isNew = Redis::set($lockKey, 'processed', 'EX', 86400, 'NX');
    if (!$isNew) {
        return response()->json(['status' => 'already_processed'], 200);
    }

    if ($event->type === 'invoice.payment_succeeded') {
        $tenantId = $event->data->object->customer_metadata->tenant_id;
        Tenant::where('id', $tenantId)->update(['subscription_status' => 'active']);
    }

    return response()->json(['status' => 'success']);
}

Sub-50ms Interaction to Next Paint (INP) Engineering

Google Core Web Vitals benchmark real-world interaction responsiveness through Interaction to Next Paint (INP). When users trigger search filters, sort e-commerce product grids, or open slide-out drawers, main-thread blocking exceeding 200ms results in poor organic ranking scores. To maintain sub-50ms responsiveness, CPU-intensive tasks—such as client-side fuzzy searching, cryptographic hashing, and tabular data sorting—must be offloaded to dedicated Web Workers.

By scheduling UI updates using requestAnimationFrame and React 19's startTransition or native scheduler.yield(), browsers render user touch and click feedback instantly while deferring background calculations until intermediate paint frames have resolved.

Modern Cache-Control & Edge CDN Invalidation Strategies

Static assets (compiled JavaScript chunks, CSS stylesheets, WebP graphics, and fonts) must be hashed deterministically (e.g., main.a9f4c.js) and served with immutable HTTP headers: Cache-Control: public, max-age=31536000, immutable. For dynamic HTML documents, deploy modern stale-while-revalidate policies across Cloudflare or Fastly edge nodes: edge proxies deliver cached HTML snapshots instantaneously to users while triggering asynchronous background fetches to origin servers whenever TTL expires.

Database Connection Pooling & Read-Replica Load Balancing

High-traffic web applications frequently saturate relational database connection limits (such as PostgreSQL's max_connections = 100). Implementing dedicated connection poolers like PgBouncer in transaction-pooling mode allows origin application servers to handle 10,000+ concurrent user connections over a compact pool of 25 physical database connections. Direct write transactions (INSERT, UPDATE, DELETE) route to the primary master instance, while read-only catalog queries fan out across asynchronously replicated read-replicas.