March 2025 Summaries

Supabase is expanding its Third-party Auth integrations to include Clerk, a popular authentication platform. This new integration allows developers to use external Auth providers with Supabase as a drop-in replacement for Supabase Auth, providing a modular design that enables users to pick and choose features of the platform. The previous method required sharing project secrets and JWT templates from Clerk, but the new implementation offers better security while maintaining the same developer experience. To get started, developers can register their Clerk domain in the Supabase Dashboard or CLI and use a simple code snippet to connect their app. Additionally, Supabase is making Third-party Auth cheaper by increasing the included MAUs on both Free and Pro plans, with pricing parity now achieved between Third-party Auth and Supabase Auth.

The Supabase UI Library is a collection of ready-to-use components built on top of shadcn/ui, designed for flexibility and ease of use. The library includes a range of components such as authentication, file uploads, and real-time features, which can be easily integrated into any Next.js, React Router, TanStack Start, or plain React app. The library is 100% compatible with shadcn/ui and follows the conventions for theming and styling. It's designed to take the time and pain out of building complex functionality like user sign-up in apps, and all components work with new or existing projects. The team plans to release more components and welcome feedback from users, who can submit ideas for favorite components they'd like to see next.

The Postgres Language Server is a Language Server Protocol (LSP) implementation for Postgres, aiming to provide reliable SQL tooling and developer experience. The initial release supports autocompletion, syntax error highlighting, type-checking, linter, and provides diagnostics. It's available via VSCode Extension, Neovim, GitHub Releases, and npm. The server architecture is designed around the assumption that the smallest unit of compilation is a single statement, with the database schema being the single source of truth for any type information. The parser uses `libpg_query` to parse SQL code reliably, while `tree-sitter` provides parsing for incomplete or malformed input. The server can process changes to the document efficiently by invalidating only affected statements and updating their ranges. Autocompletion is provided using a scoring algorithm that takes into account the changed node and CST. The Language Server is just one entry point in the project's vision, which aims to create a home for Postgres tooling and make everything accessible. Improvements to reliability will be focused on next, followed by installation guides, publishing extensions, and writing documentation to enable future contributors.

Fauna is sunsetting its product by the end of May 2025, prompting engineering teams to find reliable alternatives quickly. Supabase offers a natural migration path for Fauna users, providing a robust, scalable, and open-source alternative built on Postgres. Migration from Fauna to Supabase requires adjustments in query logic, schema definition, and overall application architecture. Supabase is an open-source Postgres development platform that provides a managed database, automatically generated REST APIs, native JSONB support, real-time database updates, integrated authentication, secure file storage, edge functions, row-level security, robust TypeScript support, full ACID compliance, predictable pricing, improved local and remote development workflows, and a global community. A two-phase approach is recommended to ensure a seamless migration: Phase 1 involves exporting data from Fauna, importing into Supabase as a JSONB data type, and rewriting Fauna API calls to use the Supabase SDK; Phase 2 involves optimizing and enhancing the migrated application, including SQL data normalization, PostgREST update, and incorporating additional Supabase features. Key considerations and trade-offs include schema flexibility, migration complexity, query refactoring, adding indexes, and thoughtful planning to ensure a seamless transition.

MongoDB's Data API has reached its end-of-life and will be deprecated by September 30, 2025. This has led to a need for engineering teams to evaluate alternatives, with Supabase emerging as a suitable replacement due to its built-in support for REST APIs via PostgREST, mirroring the core functionality previously provided by MongoDB's Data API. The transition from MongoDB to Supabase requires substantial refactoring, but offers a simplified path through automatic generation of REST APIs and real-time capabilities, authentication, file storage, and serverless functions. Engineering teams can leverage Supabase's Data API as a drop-in replacement for MongoDB's deprecated Data API, with features such as authentication, role-based access control, storage, edge functions, and more available once the data is migrated. However, careful planning and methodical execution are necessary to navigate this migration confidently, considering factors such as schema flexibility, complexity in migration, query patterns, and add indexes to optimize performance.

Supabase is announcing Dedicated Poolers, a Postgres connection pooler that co-locates with the database for maximum performance and reliability. This feature is available today for select Enterprise customers and will be generally available by March 20th, 2025. The Dedicated Pooler is an isolated instance of PgBouncer that grants fine-grained control over configuration and is recommended for serverless functions that require lower latency, better performance, and higher reliability. It offers three connection options: direct connections, shared pooler, and dedicated pooler, with the latter being available on the Pro Plan and above. Dedicated Poolers provide flexibility in choosing the right connection type for use cases, allowing developers to opt for a Dedicated Pooler for lower latency, better performance, and higher reliability when needed.