Wappler Documentation - Supabase still going places

Since my last post about them on October which I quote here:

But as for supabase- isn’t that more of a glorified Postgres?

The data store part yes. And that’s precisely the reason why I am going with them for this project. I might see myself having to use a mixed backend and use SC for certain things. Wappler should play well as it’s PG. For the frontend I will be able to take a hybrid approach with SSR and static thanks to supabase serverless functions. I will probably build the marketing side using supabase and static and the webapp using SC and SSR.

But supabase as a backend is more than PG. it’s provides a REST api using PostgREST. It is realtime via a custom built Elixir server.
It includes an Auth0 alternative and a S3 server. They are also working on server-less and a 3rd party API workflow builder similar to zapier.

Their philosophy is very similar to Wappler as they choose Open Source enterprise-grade tech and integrate into a a great product. What they can’t find or doesn’t fit they build and release to the Open Source.

But everything they reuse or build has to play nice with PG. Thus the glorified PG you mention.

and why we should integrate it

I actually don’t know if you should. That’s why I am going to test it with this project. I will report back.

They have:

Added row-level security for their realtime server.. RLS policies you write for your database are now respected by their realtime server.
Open sourced their dashboard
Acquired Logflare and they will added it to their core.
Released a native PostgreSQL extension that adds GraphQL support for PG just by reading and translating the db schema. So now on top of REST api they provided a GraphQL one by leveraging native extensions! No need for extra server.

Has anyone else given it a ride?

Community Page
Last updated: 2021-12-03T19:25:19.674Z