low-code-backend-dockered VS herbs-cli

> 1. Hasura - DB + Basic APIS, 2. Ory.sh for Auth/Authz

Great choices!

3. React on the frontend

Here I'd go with Elm, and a generated GraphL API client. Here an example to play with (which btw also includes ZomboDB for ElasticSearch integration into Postgres)

https://github.com/cies/low-code-backend-dockered

> 4. Windmill.dev

Look awesome, never heard of it. Tnx

> If you like code-focused solution: Rails, Laravel and Django are good options.

I think Kotlin/KTor, while not as full featured, is a much better alternative due to the strong typing discipline.

I was a big Rails, Ruby and dynamic typing fanboy. But then my project grew in size and I changed my beliefs.

I'd not start a big project in any language without: null-safety, proper sum-types, type inference.

Hence I like Kotlin, and KTor seems to be a good Sinatra/Flask like in that arena.

Another interesting development I find no-code/low-code tools for the backend, like Hasura. This allows me to "just expose Postgres over GraphQL" with very little code (mainly configuration). That combined with type-safe client library generation for a typesafe frontend language like Elm gives me all the power I need in a very different paradigm. Something worth considering.

Small example Hasura+Elm project: https://github.com/cies/low-code-backend-dockered

My plug: https://github.com/cies/elm-hasura-dockered

I agreed. Then did a project[1] with Hasura and a generated client lib in Elm and I'm no longer looking back. If I can get away with "no backend code" I'll do it again in a heart beat.

[1] https://github.com/cies/elm-hasura-dockered

> higher level paradigms, DSLs or a language that provides such capabilities out of the box for these reasons

Based on exactly this arguments that we created HerbsJS [1], a domain-first library to build microservices. While the essential complexity can't be removed [2], we should put effort to remove the accidental complexity as much as possible.

BTW, great to see this kind of discussion here and congratulations to the team responsible for Cell Lang.

[1] https://herbsjs.org/

Great article!

Given the absence of libs / frameworks to help in the domain part of the architecture, we created Herbs [1], where our proposal is to shift the focus of developing a microservice from the infrastructure (http, DB, logs, etc) to the domain , with an emphasis on use cases [2] and entities [3].

It may seem small but it changes a lot where you put energy into developing your software, especially maintaining it.

[1] https://herbsjs.org/

[2] https://herbsjs.org/docs/usecase/getting-started

[3] https://herbsjs.org/docs/entity/getting-started

Being productive while following the best software development practices has been one of the greatest challenges for developers. Today I can say that with HerbsJS this challenge becomes much friendlier.

Herbs CLI