My new default backend recommendation, assuming you are mainly excited about building a website/webapp that does interesting things (as most people I speak to are), and assuming you’re happy to put in somewhat more effort but learn things that are (imo) closer to best practices, is Supabase.
Supabase mostly handles the backend for you (similarly to Firebase).
It mostly asks you to configure the DB, e.g “there is a table of students where each row is a student”, “there is a table of schools where each row is a school”, “the student table has a column called school_id”.
It can also handle login and permissions just like Firebase.
I think learning to use an SQL database (like Supabase which uses Postgres behind the scenes) is somewhat harder than a no-SQL database (like Firebase), but SQL databases teach more relevant skills.
(FYI this is an opinionated take and some might disagree)
My new default backend recommendation, assuming you are mainly excited about building a website/webapp that does interesting things (as most people I speak to are), and assuming you’re happy to put in somewhat more effort but learn things that are (imo) closer to best practices, is Supabase.
Supabase mostly handles the backend for you (similarly to Firebase).
It mostly asks you to configure the DB, e.g “there is a table of students where each row is a student”, “there is a table of schools where each row is a school”, “the student table has a column called school_id”.
It can also handle login and permissions just like Firebase.
I think learning to use an SQL database (like Supabase which uses Postgres behind the scenes) is somewhat harder than a no-SQL database (like Firebase), but SQL databases teach more relevant skills.
(FYI this is an opinionated take and some might disagree)