The eventing part doesn’t seem comparable at all to Firebase: https://docs.spaceuptech.com/microservices/eventing/
It merely supports triggers versus the synchronization primitives of Firebase.
It‘s nice that a self-hosting PaaS is built again, i have the hope that one in the end will really get traction and is not dead a few month after it has been announced.
But what i really would like to see would be a self-hosted postgresql as a service. All these solutions need to reinvent this again and again. If there would be one solution with a good backup concept (!) like wal-g integrated all these new PaaS could skip the DBaaS step and just concentrate on the code as a service part. Their feature set would be a lot smaller which may lead to these projects living longer.
Tldr: We need a self-hostable PostgreSql as a Service all these PaaS could depend on.
Someone reset the counter. Just kidding. This looks pretty great!
Impressive, home page link
Which are the biggest app using firebase ? I guess firebase is gaining traction, does google reports it’s revenue ?
Looks like the architecture link in the GitHub is broken. May want to look into that.
Noob question: does this supports offline syncing like firestore?
Excellent name.
To me the whole point of PaaS is not needing to know which components are powering my app. So I don’t get what this is about.
Seems quite similar to Hasura. Looks neat.
Any opinions how this project compares to Supabase (https://github.com/supabase/supabase) in terms of audience / features, maturity and overall usefulness and performance of both?