There really isn’t a competitor. Supabase is trying to combine OSS tooling into a somewhat similar offering but it’s not nearly as feature rich as Firebase. That having been said, most people use Firebase for real time DB and auth, and Supabase supports that now. It doesn’t, however, support offline use cases, or any of the advanced functionality of firebase.
Pouch and couch solve the offline data scenario and live replication, but no auth story and the mapping of users to data is problematic (unless you build a proxy layer, there’s not an easy way to have some data be public, some private, and some shared).
Realm is paid these days, I believe, and it solves the data replication, but again, no auth.
I'm the founder of Supabase. We started this year, so we definitely have a lot more work to reach feature-parity with Firebase. Since we are using existing OSS products though, we're moving pretty fast.
We have made some technological decisions which we feel are better than firebase too. A developer sent us a note today that they converted a query from Firebase to Supabase and the result was a reduction from 27.9 seconds to 1.3 seconds. This is because we are building on top of Postgres. We also benchmarked our smallest servers yesterday - we were getting around 1200 reads/s on our smallest servers (FB was doing 1540 reads/s). We aim to get closer to 2K over the next 1 month and we'll publish the benchmarks.
> It doesn’t, however, support offline use cases
This is correct - it could take a few more months to get this out. Right now we're focused on stability/performance.
Agreed and unfortunately Realm appears to have been acquired by mongo. No disrespect to the mongo team, but if we've learned anything from firebase it's that whenever a project like this gets acquired things get a little... shaky.
Yeah, I still use Parse over Firebase in all my "full stack" work. I used to teach Firebase database to polytechnic students, and most of them had trouble with it even when given months. Parse Server was very easy to teach, and nearly all of them set it up within a day.
The solution is likely to arrive in the Clojure/ClojureScript ecosystem before it arrives anywhere else because tools like Datascript lend itself to this type of thinking, e.g. 3DF: https://github.com/sixthnormal/clj-3df/
The closest thing we have to streaming updates right now is FactUI, which uses the Clara rules engine, but it's IMO hampered by limitations of Clara and Cljs namespacing: https://github.com/arachne-framework/factui
The RETE algorithm is a less general solution to incremental updates. Zach Oakes is doing some interesting work with O'Doyle Rules: https://github.com/oakes/odoyle-rules
Plug: I wrote a small clojurescript wrapper around firebase. You can try it out here. -> https://firemore.org/
I haven't found another solution that can get you started as quickly as Firebase can. Most common complaint I hear from developers about Firebase is the concern that Google will drop support at some point. I can't fault that concern, but Google seems to drop developer products at a much lower rate than customer products.
[+] [-] lukevp|5 years ago|reply
Pouch and couch solve the offline data scenario and live replication, but no auth story and the mapping of users to data is problematic (unless you build a proxy layer, there’s not an easy way to have some data be public, some private, and some shared).
Realm is paid these days, I believe, and it solves the data replication, but again, no auth.
[+] [-] kiwicopple|5 years ago|reply
I'm the founder of Supabase. We started this year, so we definitely have a lot more work to reach feature-parity with Firebase. Since we are using existing OSS products though, we're moving pretty fast.
We have made some technological decisions which we feel are better than firebase too. A developer sent us a note today that they converted a query from Firebase to Supabase and the result was a reduction from 27.9 seconds to 1.3 seconds. This is because we are building on top of Postgres. We also benchmarked our smallest servers yesterday - we were getting around 1200 reads/s on our smallest servers (FB was doing 1540 reads/s). We aim to get closer to 2K over the next 1 month and we'll publish the benchmarks.
> It doesn’t, however, support offline use cases
This is correct - it could take a few more months to get this out. Right now we're focused on stability/performance.
I'm happy to answer any other questions
[+] [-] __composed|5 years ago|reply
[+] [-] digianarchist|5 years ago|reply
https://parseplatform.org/
[+] [-] xgenecloud|5 years ago|reply
An open source alternative of Parse for SQL databases : https://github.com/xgenecloud/xgenecloud
* Instantly generates REST APIs & GraphQL APIs on 'ANY' MySQL, PostgreSQL, Microsoft SQL Server, SQLite & MariaDB databases.
* Has a built in GUI to design SQL schema which auto-generates reversible schema migrations.
* And lastly, the entire backend generated can be even deployed as a Lambda Function or GCP Cloud Function or Azure Function App!
Demos are below : Happy to answer any questions
[1] : GUI based schema designer : https://www.youtube.com/watch?v=ETEEcY4mmEg&list=PLhQvP2JTFb...
[2] : REST API creation : https://www.youtube.com/watch?v=gEU-QvmwSKQ&list=PLhQvP2JTFb...
[3] : GraphQL API creation : https://www.youtube.com/watch?v=qaLIpXe1gb0&list=PLhQvP2JTFb...
(full disclosure : Im the Founder of XgeneCloud)
[+] [-] muzani|5 years ago|reply
[+] [-] kgraves|5 years ago|reply
[+] [-] wtfrmyinitials|5 years ago|reply
[+] [-] pgt|5 years ago|reply
And keeping a close eye on Differential Dataflow: https://github.com/TimelyDataflow/differential-dataflow/
DD is commercialized in Materialize: https://materialize.io/
The solution is likely to arrive in the Clojure/ClojureScript ecosystem before it arrives anywhere else because tools like Datascript lend itself to this type of thinking, e.g. 3DF: https://github.com/sixthnormal/clj-3df/
The closest thing we have to streaming updates right now is FactUI, which uses the Clara rules engine, but it's IMO hampered by limitations of Clara and Cljs namespacing: https://github.com/arachne-framework/factui
The RETE algorithm is a less general solution to incremental updates. Zach Oakes is doing some interesting work with O'Doyle Rules: https://github.com/oakes/odoyle-rules
[+] [-] pgt|5 years ago|reply
Differential Dataflow + Datomic solves this problem.
[+] [-] tarun_anand|5 years ago|reply
[+] [-] dm7|5 years ago|reply
[+] [-] stephen_cagle|5 years ago|reply
I haven't found another solution that can get you started as quickly as Firebase can. Most common complaint I hear from developers about Firebase is the concern that Google will drop support at some point. I can't fault that concern, but Google seems to drop developer products at a much lower rate than customer products.
[+] [-] danlugo92|5 years ago|reply
https://www.gun.eco/
[+] [-] unknown|5 years ago|reply
[deleted]
[+] [-] Arkdy|5 years ago|reply
https://github.com/jacobobryant/biff
[+] [-] pier25|5 years ago|reply
It doesn't have sync or realtime yet, but it's a much better database overall.
[+] [-] exhibitapp|5 years ago|reply
[+] [-] xrd|5 years ago|reply
[+] [-] Wintereise|5 years ago|reply
[+] [-] dmd|5 years ago|reply
[+] [-] habeyer|5 years ago|reply
[+] [-] girishso|5 years ago|reply
[+] [-] wh-uws|5 years ago|reply
[+] [-] trysomechai|5 years ago|reply
[+] [-] bribri|5 years ago|reply