Ask HN: Would you use a Low-effort Microservice Builder?

I am currently building a low-effort microservice builder. I am interested to know if you share the described problem. Also please comment if you find the solution to solve the problem. Thanks!<p>Promise an easy and fast way of building and deploying a microservice<p>Problem microservice development is a lot of work: for instance, you need to provision your infrastructure, manage secrets, configure access control, configure network, design and configure your system components, develop your app with public api, business logic, and data persistence, and also pay bills. And repeat this for every new project...<p>Solution start with something less complex: something that is easy and fast to develop and test, and convenient to deploy. Something that you can later switch to a full-fledged implementation, when you actually know what you need to implement.<p>My builder technology enables...<p>development build: build microservices using high-level programming abstractions and browser-based ui test: consistent testing using exactly same code but different configuration values (in profiles) deploy: one-click deployments to private or public cloud<p>layers api layer: spec-first API development (openapi v3 spec) logic layer: write your logic using high-level functions (DSL) data layer: data connections and (JSON) objects are accessible via name. There is no internal data persistence, but supports many types of external data sources (with authentication)<p>code loops: supported variables: supported conditions: supported<p>What do you think?