Dev tool for building modern backends in a frontend style

Hey everyone, I'm a full-stack dev and I've been wanting to build a tool to build backends for front-end and full-stack devs that aren't 100% familiar with the nitty-gritty of cloud development (or don't want to bother). Since yall would be great first users I'd like to float out my design goals and mocks to see if you're interested before I hack away:

--Design goals

1. Follow in Rails' footsteps whenever possible (https://rubyonrails.org/doctrine/). Users should be able to get something working quickly without much fuss leaning on convention.

2. Lean into front-end development techniques/technologies. EX: Typescript/Statelessness/Event-driven.

3. Abstract over infrastructure: the user should just bring code. Users without cloud knowledge should be proficient. This is the delta from existing tools like Serverless Framework and Apex. Those tools require users to know things like what APIGateway is and how it works; this tool would just have some "Http" library that uses APIGateway under the hood with sensible configuration.

4. Have a strong open source extensibility story. The tool and its libraries should be 100% open source.

5. Be opinionated about the backend but UNopinionated about the front-end. Users should be able to bring their frontend of choice. As a side note: building the frontend is out of scope; devs already know how to do this. Hosting the frontend (optimally!) is in scope.

6. Target developers; expect basic JS proficiency and allow for JS experts to leverage their skills.

--Implementation

Here's what I've been thinking and working on a prototype towards:

Users build their business logic and data transformations in JS/TS functions, then the user writes code in the framework that wires the functions together. Mock code examples:

//execute a bespoke database query inside getUsers
Http { method: "get", path: "/users" } => "./getUsers.js"

//Let users write their own event libraries
include "UserRegistration"

//Let users include 3rd party event libraries and "services"
include "Gmail"

UserRegistration.newUser -> "./sendUserEmail.js"

The framework could be another language that sits in configuration files outside your project, native to JS/TS, or a visual programming environment. Not sure which is better right now.

--Outstanding questions

A) Databases, how do they work?

B) Interop with existing backends?

C) Interop with existing tools (docker/terraform/cf/serverless framework)?

D) Operations...

E) I've thought about making this low-code and adding a visual programming environment on top so that less technical people can use it--not sure if this is a good idea.

Thanks for the feedback!

#tech-questions