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.
This is just a feature idea (and perhaps if I have time I'll draw up a PR), but since most folks interacting with Supabase are using Phoenix/Ecto already so it would be nice to configure it with a Repo module and/or database_url rather than a keyword list.
> 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
also follow up question, is Supabase using one database per "app" (one cluster) or are there a few different elixir apps that are being backed by the same database (multiple independent clusters)? Though I wonder if using the same storage location for multiple clusters conflicts with how libcluster strategies work.
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