Supabase for an Event-Driven Architecture
Let's say you are building a machine learning cloud platform: relatively small amount of users deploying heavy training jobs to serverless platforms.
You have a web-based frontend with your favorite framework, and a couple of Python microservices talking with external platforms to orchastrate the jobs.
Is it a crazy idea to use Supabase as the central source of truth without any kind of REST API in front of it? That is, have the frontend as well as every microservice directly use the Supabase client?
To go further, would it be sane to make this an event-driven architecture where services use the realtime feature to trigger tasks amongst one another?
You have a web-based frontend with your favorite framework, and a couple of Python microservices talking with external platforms to orchastrate the jobs.
Is it a crazy idea to use Supabase as the central source of truth without any kind of REST API in front of it? That is, have the frontend as well as every microservice directly use the Supabase client?
To go further, would it be sane to make this an event-driven architecture where services use the realtime feature to trigger tasks amongst one another?
