Jooby VS lumen

One of the good things about it is that using asynchrony is optional. If you don't have to call out anywhere to build the response, processing can all stay in the handler's calling thread. If you do, you can return a future and have the library handle the async for you.

One downside is that it is based on Jetty which isn't considered the most performant backend. A lib with a similar API but based on Netty is Jooby [1] which scores well in the Techempower benchmarks.

[1] - https://jooby.io/

Jooby and Helidon SE are among the best.

The code snippet gave me a vibe like it was jooby Looks cool, I suggest maybe start incorporating Project Loom virtual threads in the future.

Speaking of backend development, recently I gave Jooby[1] a try after discovering it was one of the world's top performer in Tech Empower's web framework benchmark[2].

Surprisingly enough, it's terribly easy to put together a REST API with Jooby. I wonder why it's adoption rate is so low.

[1] https://jooby.io/

[2] https://www.techempower.com/benchmarks/

Do you need to use Spring btw? If you want to broaden the tool selection I've had great success with i.e Jooby (https://jooby.io/) together with Kotlin coroutines. Another alternative is the KTOR framework.

Jooby I think is the best bet. https://jooby.io/ watch out for jooby dot org I think someone sniped the domain.

Spring Boot or JAXRS. I personally use Jooby a lot which is similar in style to spark but has annotation support and isn't a singleton.

There are details on this also: https://github.com/GetFirefly/firefly#runtime

Generally it should be assumed that actors and their concurrency model is fully supported as that is a part of the core semantics for BEAM languages.

I think this project used to be called Lumen until pretty recently - https://github.com/GetFirefly/firefly

Probably not a practical solution for what you are building now, but it's worth pointing out Lumen, an Erlang VM implementation that compiles to WebAssembly, and could one day enable Elixir on the frontend.

Another vector could be some tooling that makes it easy to run Go programs compiled to Wasm run inside of Wasmtime environment hosted in Rust. If we run the go tooling in the same system, one could point this tool at a Go repo and be running that Go in a matter of milliseconds. A fun feature would be running channels across separate Wasm envs. Or maybe use Lumen.

Wish the Elixir WASM project -- Lumen -- were active. It seems like nothing much is happening on it.