@Lucas G that’s an interesting question. For the moment I’m investigating multiple solutions; the end goal is to « teach » users to build a new web app that leverages a database and a middleware (the middleware being Make).
Normally, the web app won’t access the database directly but will use webhooks to get or update any backend data. I still wanted to test an hybrid mode where the front would mix calls to webhooks and to the database, but it’s not a good idea, all calls should go through webhooks in my case.
Now to answer your question ☺️: I also tested Supabase, but the way their API works makes it a little more complex for Make. If I want to call it, I need to first get the session token and then make the actual call, which means two calls each time I want to interact with the database. I could store the session token in the Make DataStore or as a global variable, but I would need to maintain it, which would be complex.
One other way to overcome it, is to build a Make Custom App, because in that case, we can benefit some automatic token refresh mechanisms. But we don’t plan to have users build their own Custom App.
And because Make has a Baserow native App, it’s a lot quicker and easier to send queries to it.
And personally I found Baserow less complex to learn than Supabase.
I hope I’m clear 😅
