Koa VS LoopBack

Since "Express.js is an old framework that has not evolved for a long time. It's not a good choice for new projects since it can easily lead to security issues and memory leaks." -- H3. Which is also the case for Koa.

In this example, we're using the serverless framework to quickly set up the Lambda function along with an API gateway for the entry point. The lambda function is a simple Koa REST API with a few functional endpoints.

The initial step is to create our entry point, from where the page will be rendered. In this case, we will use the koa framework.

Koa.js: By the team behind Express, Koa.js utilized async/await for middleware, resulting in cleaner and more readable code.

Koa

Koa.js: https://koajs.com/

Koa -Next Generation Node Microservice Framework

Backend is more tricky. - RESTful APIs I prefer Koajs - For a RPC/microsevice, I have only used gRPC - For a CLI, yargs and inquirer

There are lot of different frameworks out there. If you learn one, there is no guarantee that the next job you find will use the same. For example if you learn Express and the next one used Koa or Nest.

Koa.js is a minimal and flexible Node.js web application infrastruc­ture, which provides a robust set of features for web and mobile applica­tions. It is an open-source framework developed and maintained by the creators of Express.js, the most popular web framework for Node.js.

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: