filipecabaco

Supabase | Senior Elixir Engineer | APAC | Remote | https://supabase.com/

We're hiring to grow our Elixir teams mainly on Supavisor and Realtime projects. You will be using Elixir and also help build new client libs mainly in TS. We work in an opensource manner so you can check our code in https://github.com/supabase/realtime and https://github.com/supabase/supavisor.

* Senior Elixir Engineer: https://jobs.ashbyhq.com/supabase/46ffc00b-b9a7-4b45-a6f2-1a...

Any question, email me at filipe@supabase.io

currently one database per app but indeed that is a good question, I hope people will test it out and find those caveats so we can improve on it

There are many libcluster adapters already, so what pushed Supabase to make a database backed one? What is the advantage?

usually the strategies are focused on the cloud provider and since we want to keep it adaptable to multiple cloud providers it felt that using one of those strategies would not be the way to go.

another factor was the fact that we already use heavily postgres in all our projects so if that is available to us we should use that instead

I know Supabase has hooks (https://supabase.com/docs/guides/database/webhooks) so is the hope to leverage that tech to trigger something whenever a new node connects?

we already have a presence system available for users in https://supabase.com/docs/guides/realtime/presence using phoenix presence

Repo module and/or database_url rather than a keyword

Good call! we should have more flexible configuration options

supabase team here

eager to hear your feedback, thoughts and questions!

awesome news! that has been pending for some time in the issues section

now they just need to embrace 2-step auth ...