LoopBack VS feathers

Backend is usually an API you design, can simply use Rails for this, basic Express.js or some framework like https://loopback.io/ if you want javascript otherwise you want 'system design' https://github.com/donnemartin/system-design-primer for all the load balancers/dbms if that's what you mean.

LoopBack – Highly Extensible Node.js and TypeScript framework

We deliberately decided not to use "kitchen-sink included" frameworks such as Laravel, Django, Loopback or Nest.js to keep things simple.

Loopback

I'd say check out https://loopback.io

This interface defines the basic CRUD capabilities that any entity should provide. This contract is based on frameworks like Loopback, Django RF, RoR and Spring. The Service.kt looks something like:

For backend this might help https://feathersjs.com. I’m not affiliated with them, just a happy user.

Community stats: Feathers.js has a small but active community with 14.8k stars and 761 forks on GitHub.

The project has gained almost 15k GitHub stars and 26k npm weekly downloads. The Feathers library is widely known for its simplicity and ease of integration with various databases, and it also comes with excellent documentation to help you get started.

Feathers.js - fully fledged backend framework, with almost anything out of the box

Feathers.js

For anything CRUD or that can be modeled as such, I use FeathersJS (https://feathersjs.com/).

Feathers – Realtime Node Microservice Framework

Is there something like Feathers | The API and Real-time Application Framework (feathersjs.com) ?