Ecto Plugin — Uni

defmodule MyApp.Repo do use Ecto.Repo, otp_app: :my_app use UniEcto.Plugin, prefix_key: :tenant_prefix def all_tenants do # Could be a DB query or a static list ["public", "tenant_customer_a", "tenant_customer_b"] end end Step 3: Generate the Tenant Migrations The plugin usually provides a generator:

| Library | Strategy | Best For | | :--- | :--- | :--- | | | PostgreSQL Schemas | Most Elixir SaaS apps (Gold standard) | | Uni Ecto Plugin | Custom (Configurable) | Developers needing fine-grained control | | Apartment (Rails) | Row-level (Legacy) | Not recommended for Elixir | | Ash Framework Multi-Tenancy | Resource Layer | Large, complex domain models | uni ecto plugin

In the modern landscape of Software as a Service (SaaS), multi-tenancy is no longer a luxury—it’s a necessity. Whether you are building a white-label CRM, an enterprise ERP, or a simple API for startups, you need a way to isolate customer data securely. defmodule MyApp

:ok, prefix end The uni_ecto_plugin often bundles a caching mechanism. Setting a tenant prefix usually involves a database lookup to validate the tenant exists. This adds latency. Setting a tenant prefix usually involves a database

defmodule MyApp.Plugs.TenantResolver do import Plug.Conn import UniEcto.Plugin, only: [set_tenant_prefix: 1] def init(default), do: default

The uni_ecto_plugin provides a migration helper:

conn end