DEV Community

Cover image for Why would you use Backend as a Service (BaaS)?

Why would you use Backend as a Service (BaaS)?

BekahHW on February 09, 2024

Today is day 9 of my 29 Days of Open Source Alternatives series, where I'll be exploring open source alternatives to proprietary software in the ca...
Collapse
 
lyatziv profile image
Lavi Yatziv

Having used Sanity as a backend. I feel like it at least deserves mentioning. It's very customizable and has a built in CMS for in-house teams to use. Couple that with the version control options and user level access controls. It's quite adaptable for many projects.

Collapse
 
lymah profile image
Lymah

So relatable! Thank you for sharing.

Collapse
 
sectasy0 profile image
sectasy

AppWrite does not seem to be as powerful as Supabase.

Collapse
 
bekahhw profile image
BekahHW

Can you expand?

Collapse
 
sectasy0 profile image
sectasy

Sure, Supabase utilizes PostgREST as its underlying technology, granting you unrestricted access to your assigned database. Unlike AppWrite, there are no limitations imposed on writing custom functions in SQL, which can be subsequently referenced through the API. AppWrite, on the other hand, confines you to using edge functions for any required customizations. Additionally, it appears that AppWrite employs a NoSQL database, at least in the user-provided information. In terms of authentication capabilities, Supabase outshines AppWrite by offering robust options for configuring any OAuth Provider, facilitating seamless logins. While my knowledge is based on the free plan, differences in the paid plans might exist.