Supabase has grown a lot 1 since last Launch Week, but it wouldn't be possible without some amazing open source tools. Since we're shipping a few upgrades this week we feel it's only fair to shine a spotlight on some tools and community efforts that make Supabase possible.
PostgreSQL version 13.3
PostgreSQL is a big part of Supabase, and it's also a huge inspiration - the speed that they ship, their community organization, and their absolute dedication towards reliability. PostgreSQL 13.3 was released in June and (from today) every new Supabase project will be on PostgreSQL version 13.3.
Supabase makes it easy to get started with Postgres, but we think you should try it even if you don't want to use Supabase. Here's a few ways we make it easy to use PostgreSQL without Supabase:
- Supabase was the first company to put Postgres in the Digital Ocean Marketplace. Since then it's been installed over 1000 times (not by us!).
- We provide a Postgres image in the AWS marketplace.
- We're packaging the Marketplace version, along with "Bundles"
- We're developing a few extensions: supautils, pg_net, and a couple more soon to be announced.
PostgREST version 8.0
This new PostgREST stable version comes with the improvements we've made to make it truly enterprise-grade. Due to our commitment with OSS, all of our improvements are upstreamed, so you can fully use them on your own self-hosted projects.
Improved Performance: Due to Supabase's high throughput requirements, PostgREST 8.0 handles up to 50% more throughput on GET requests, according to our benchmarks. We converted all SELECT queries to use prepared statements and reduced logging verbosity to make this possible.
Reduced downtime: we need PostgREST to be more "set it and forget it", so reloading schema cache now has zero downtime.
Dynamic Configuration: we've made it easier to handle PostgREST configuration at scale (we manage thousands of PostgREST instances).
This new version includes the ability to use an in-database configuration that is reloadable through a
Less admin burden: PostgREST previously required the
pg_listen utility to reload its schema cache. This is no longer needed.
The schema cache is reloadable with a simple
Better diagnostic information: in the rare cases where PostgREST fails, we want to find the exact root cause quickly. For this we've improved its logging by adding logging levels and timestamps to all server errors.
Simpler OpenAPI: showing a complete OpenAPI output used to require a highly-privileged
anon role. With the new
this is no longer needed and
anon can be kept with minimal privileges.
The community has made many more enhancements and bug fixes for the new version. See v8.0 CHANGELOG for the full list.
Want to get started with PostgREST? The Supabase community has built a number of client libraries to make it simpler to use:
- Rust: postgrest-rs
- Go: postgrest-go
- Python: postgrest-py
- Dart: postgrest-dart
- C#: postgrest-csharp
- Swift: postgrest-swift
- Ruby: postgrest-rb
- Kotlin: postgrest-kt
- Help with PostgREST development.
- Help with PostgREST docs translations.
- Follow the official PostgREST Twitter account.
Supabase Flutter/Dart (Beta release)
Today the Community are releasing both the Flutter and Dart libraries in Beta (with a bit of help from the Supabase team).
- Check out the Flutter Quickstart Guide
- Check out the code:
OK, OK, we get it - GitHub Discussions aren't enough for y'all. While we've been trying to keep the conversation contained to our GitHub org, the community has been creating subreddits, StackOverflow tags, and GitHub topics.
A few weeks ago one of the community created a Community-led Discord, and so the team figured we might as well join the fun.
We'll still be using Discussions for debugging, but if you're looking for a place to hang out with Supabase developers, Discord is where to find it.
Join the Supabase Community Discord: discord.supabase.com, say hi, and start building.