4 ms·

Supabase wrote their backend in Elixir. AFIK, their offering started as essentially “various stuff common in Elixir systems, as a service for JS devs”. More he

• reducesuffering 4y ago
  Yes, some portion of their backend is Elixir/Phoenix: https://github.com/supabase/realtime https://github.com/supabase/realtime but most of their current stack and active development, frontend and backend, is Next.js, and not the Rails/Phoenix fullstack way: https://github.com/supabase/supabase https://github.com/supabase/supabase
  • kiwicopple 4y ago
    I just did a full write up on the Architecture becaase we have this question often: https://supabase.com/docs/architecture#architecture https://supabase.com/docs/architecture#architecture > most of their current stack and active development, frontend and backend, is Next.js This is only the Dashboard. We dogfood Supabase to build Supabase, so we use the tools in the doc above
    • reducesuffering 4y ago
      No better clarification than the author! In my mind, I was thinking of just the web framework UI-for-CRUD comparison, where Next.js is supplanting what Rails is typically used for (like your Dashboard / GUI, and most of the core webapps for the previous 2010 Rails co's), but fair enough, you're probably leveraging a lot more of your own PostgREST, triggers, functions, & webhooks than a typical backend Next shop.