Can't Decide on a Backend

#backend #nocode #database #headlesscms

I'm trying to build an application that will have a web application and also mobile applications (iOS and Android) eventually.

I don't know anything about backends, and I've seen different nocode / low code backend solutions, as well as headless CMS.

Can someone explain the difference between some of these no code backend solutions e.g. BudiBase and headless CMS e.g. GraphCMS ?

Also, can I use any of these as a centralised database that will feed both the web and mobile, or should I just stick with something more traditional like Firebase?

It doesn't have to be the specific examples I gave, but there are so many options, I don't know what to pick.

I'm planning to build the web front end with WeWeb (weweb.io), or possibly Bubble.

Thanks.

Top comments (3)

codewander • Apr 8 '22

CMS for large text heavy data, such as a newspaper or article publishing web application... Firebase et al for small, simple data to back a mobile app....hasura et al for slightly more power and structure... postgres + some graphql or rest server for full power, flexibility

codewander • Apr 8 '22 • Edited

For last option, I would use rest server, probably Django rest framework, rails API, flask + sqlalchemy, or gin + gorm. I only have light experience with rails, haven't used the other two options.

Areskul • Apr 8 '22

I would recommande Supabase

An Animated Guide to Node.js Event Loop

Node.js doesn’t stop from running other operations because of Libuv, a C++ library responsible for the event loop and asynchronously handling tasks such as network requests, DNS resolution, file system operations, data encryption, etc.

What happens under the hood when Node.js works on tasks such as database queries? We will explore it by following this piece of code step by step.