I would really love to see this too. If someone could write a guide, just post here what they’ve done or good resources they found, that would be much appreciated.
Strapi has great functionality as a Content Management System.
Supabase allows me to do all that other fancy back-end, high-performance and low-level stuff for my project (I love their database functions and their batteries included back-end).
In my use-case, an e-commerce where products, blog posts, media, etc can be managed in Strapi (storage-like, rarely touched, less performance needed as stuff would mostly just get fetched on build-time).
Then let orders, customers, shipping, financials, etc be handled through supabase (performance-focused).
Somewhat separation of concerns, with some interoperability as orders still need some of the product data.
I want Strapi to sit next to or on top of Supabase, to have them work in tandem on the same database as their shared source of truth.
Having them share the same database just means less duplicating of data, code to make the two communicate and sync, and probably over-all costs. It just feels nice to have one database as the one source of truth for my project that still allows me to use both Strapi and Supabase on top of it, as the great tools they both are.
Please let me know your view of it all, criticize my idea and tell me how it could be achieved.