Vote for more Databases

[kiwicopple]

This issue is for tracking requests/demand for different databases. Give a comment a thumbs up if you want us to build Supabase for your favourite database.

Please refrain from adding comments unless you are adding a database which isn't already listed.

[kiwicopple]

PostgreSQL - supported!!

[kiwicopple]

MySQL

[jdgamble555]

From my understanding, mySQL should be the main database instead of postgreSQL, since it is not a distributed database. Supabase claims to be Firestore's competitor, but postgreSQL does not scale well horizontally.

[organicnz]

Would be Supa useful as there are so many WordPress websites that would def switch to Supabase MySQL :)

[kiwicopple]

SQLite

[rnbokade]

Absence of postgrest like project for same will be the biggest issue I guess.

[barakplasma]

Directus manages to provide graphql from sqlite

[c00kiemon5ter]

Litestream is now a thing atop sqlite
https://litestream.io/

[tunecino]

This could help with offline support (#357), specially after SQLite adding JSON type the same way PostgreSQL is handling it. With raising tools like Tauri already working on mobile support, SQLite & ways to sync to PostgreSQL may be huge for the future.

[CanRau]

Just wanted to mention that this might be interesting for support of Cloudflare D1

[ajwerner]

CockroachDB

Cockroach is PostgreSQL wire compatible and has good and constantly increasing compatibility. Generally in places where there are incompatibilities there are easy workarounds. It should be very easy to support, in fact, it might just work. Cockroach has online upgrades, online schema changes, and is replicated for high availability and some other advantages over Postgres.

[spencerbart]

This would be awesome. We are looking for something super scalable.

[KFree98]

Has Anyone tested the plug and play compatibility on crdb with supabase?

[clibequilibrium]

Sadly cockroachdb has not RLS yet...

[Rizzist]

Still Waiting for this
Only thing keeping me from jumping unto the Supabase Boat!

[vim951]

+1

[JCKodel]

MSSQL

[bit-burger]

Its closed source, so there's no point

[huperniketes]

If Supabase hopes to be used by enterprise shops, support for existing enterprise infrastructure will be necessary.

[kiwicopple]

Thanks for all the interest here.

Just a small update that we are 100% committed to Postgres right now. And we're deeply integrating with some of the features Postgres has to offer (particularly auth). Cockroach is interesting to us since it's wire-compatible, but we still have a lot of features to build and supporting even 2 databases will slow us down immensely.

Keep the suggestions coming though! When we reach 1.0 we will loop back on this one

[spencerbart]

Cockroach would be awesome. Any updates on Cockroach?

[nbaua]

Thanks for all the interest here.

Just a small update that we are 100% committed to Postgres right now. And we're deeply integrating with some of the features Postgres has to offer (particularly auth). Cockroach is interesting to us since it's wire-compatible, but we still have a lot of features to build and supporting even 2 databases will slow us down immensely.

Keep the suggestions coming though! When we reach 1.0 we will loop back on this one

In that case. it seems you guys are a bit early. I liked your enthusiasm though. Keep the ball rolling.

[aridwiprayogo]

Redis

[jdgamble555]

redisgraph if we go that way!

[ioucyf]

redis is a must in my opinion, and the entire redis stack if possible! 🙏🙏

[itsezc]

ArangoDB

[gpproton]

Oracle

[bit-burger]

This is (as well as Microsoft SQL) closed source, so there's no point

[huperniketes]

If Supabase hopes to be used by enterprise shops, support for existing enterprise infrastructure will be necessary.

[mmpneo]

Mnesia

[juan040]

DynamoDB

[miso-belica]

https://www.yugabyte.com/ is also compatible with PG but has some features similar to CockroachDB.

[ronasuti]

This is a really great one, as YSQL has even greater compatibility than CDB. For example, Hasura works OOTB with YSQL, but currently doesn’t support CDB, mainly as Hasura needs features like triggers. If CDB is not working for those reasons, YSQL probably would. It’s only problem is that it does not support gist indexes at all which could be a problem for spatio-temporal tables (GIS, reservation systems, etc.)

[FranckPachot]

YugabyteDB is the most PostgreSQL compatible within the distributed SQL databases, as it reuses postgres code, but there's still a few things in progress that are used by supabase (PG14 features, GIST, some extensions). @kiwicopple I don't know how those features are mandatory or can be worked around but could be interesting to list them

[kneeraj]

We ( Yugabyte ) are currently exploring YugabyteDB with Supabase ( YugabyteDB Github Issue ). There have been few requests for this from the community on our side as well.

[wawilation]

My vote is with YugabyteDB as well.

[dcaoile]

Raising my hand and standard for YugabyeDB! 🚀

[benmccann]

AWS RDS & Aurora

[bit-burger]

How is that even supposed to work with an open source Projekt like Supabase?

[okadts]

Same question here. I also ask the AWS support and they are not sure that it will be compatible.
Even though I send them this link https://supabase.com/blog/2021/07/26/epsilon3-self-hosting where it said that use AWS RDS.
The AWS support team encourage us ask back if the third party (Supabase) support AWS RDS or just use the EC2.
Any though on this @kiwicopple , should we use the EC2 (docker method).
Thanks

[stephanelpaul]

Mnesia

oufff erlang stuff

[duncanhealy]

MongoDB

[arthurmougin]

MongoDB Atlas Search is a league ahead of Postgres FTS, yet lack the developer experience of Supabase, self-documenting API. Connecting both would allow us to take the best of both world.

[ghost]

TimeScale

[ghost]

QuestDB

[o624366705]

Mysql

[killshot13]

Mysql

#6 (comment)

[grind-t]

EdgeDB looks promising. It's an open-source object-relational database built on top of PostgreSQL with native GraphQL support.

[prescience-data]

Just saw this too - this would be super cool to get the EdgeQL magic along with Supabase's Auth.
Reference: https://www.edgedb.com/docs

[ild0tt0re]

Wow! In one word "the future".

[devi-prsd]

They got their own auth now and cloud, I'm hoping they speedup as fast as postgres.

[noriakisana]

InfluxDB - for timeseries

[de1mat]

CouchDB

[vphaneendrayb]

Yugabyte - for Distributed SQL

[ngaut]

TiDB - open-source, cloud-native, HTAP database for elastic scale and real-time analytics

[c00kiemon5ter]

A temporal database.

There is a different world of features and niceties around temporal databases (like datomic, xtdb or datahike) which I find super interesting to be able to work with within an application. The nice thing about such databases (aside from database-branching, as-of "time-travel", etc) is that you can use the same data source to do analytics. This would bring supabase closer to a feature-full firebase alternative.

AFAICT, datomic is propriatery, xtdb is a big complex system but there are more smaller ones coming up. I cannot recommend one, but there is an interesting thread on the different choices and features over at: athensresearch/athens#9

It seems biff is trying to find its position in that space, but I feel supabase is more focused with better choices and tooling underneath, but most importantly an active community.

Now, to be pragmatic, I don't expect supabase to suddenly switch over to these systems, but I do think there are lessons that can be learnt and features that we could try to think how to get them through supabase and postgres, and I think that would give a lot of leverage to supabase.

[c00kiemon5ter]

Another clojure based open-souce choice is Fluree:
https://flur.ee/

[c00kiemon5ter]

TerminusDB seems to be a non-clojure open-source contender in this space:
https://github.com/terminusdb/terminusdb

[davidhmays]

Could you explain what you mean by being able to use the same datasource to do analytics? Can't you do analytics from any datastore, what makes the temporal databases better at this? I'm trying to decide between diving into XTDB, or learning EdgeDB, and part of that is trying to decide if I really need XTDB's advertised bitemporality, or if EdgeDB's time datatypes are all I'd really need. (And do either of these or Datomic support geospatial data?) Also trying to decide if I really need XTDB's schemaless, or am fine with EdgeDB's excellent migrations. Both seem great, but diving into one or the other is such a different paradigm instead of actually learning anything I worry about deciding on one haha. Liked the marketing behind Surreal, but the documentation isn't ready and the EdgeDB and XTDB docs are pretty good.

[c00kiemon5ter]

Alternative to Materialize?
https://materialize.com/

[BhaskaranR]

has anyone tried AlloyDB? looks to be fully compatible with postgres.

[weburnit]

I tried, it works a half. the service_role/anon is possible to query the table on postgrest.

[weburnit]

can not use logflare! because it doesn't allow to have wal_sender

[Manas-Nagelia]

SurrealDB.

[axscell]

That would be awesome if implemented!

[deezed420]

SurrealDB. That would be a nice addon to the SurrealDB app too.

[xuman2019]

DB3 Network - Decentralized Firebase Firestore Alternative.

[Shalashtein]

Fluree

A database for collaborative clean extensible composable data built for data centric systems where agents are the largest consumers and producers of data.

JSON-LD document based
Knowledge graph triple-store
Programmable data (policies and contracts...)
Cryptographically proven identities

[arghaffari]

Neo4j