> 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

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.