zio-http VS project-loom-slides-and-demo-code

For JNI, make sure you have `-H:+JNI` in your native image options. Be aware that Netty is a bit of a monster to include in a native image application (I just recently added it a Netty dependency and it completely broke my project and took a good day to figure out). Mine was through zio-http and I was able to piece together some working options from github issues: https://github.com/zio/zio-http/issues/20.

What's the hardware being used for your test? I get 55k RPS with a basic 200 responder with zio-http[0] (which uses Netty) on my i5-6600K, and over 20k RPS for an e2e POST endpoint that does write batching to postgres (committing the insert before responding with the db generated id). Postgres, client (vegeta[1]), and the app all on the same machine. I think that was with keep-alive, I think like 256 clients for the basic responder and 1024 for the one that writes to the db. There's a recently merged PR for zio-http that does 1M req/s on whatever machine they test on[2] so Netty can absolutely scale to high RPS.

[0] https://github.com/zio/zio-http

[1] https://github.com/tsenart/vegeta

[2] https://github.com/zio/zio-http/pull/1659

Yep! https://github.com/zio/zio-http

I was looking at HTTP frameworks for Scala. I found zio-http, https://zio.github.io/zio-http/. Has anyone tried this framework?

https://github.com/dream11/zio-http very simple and super performant, dead easy to abstract over routes to make a router

I'm starting a new project, essentially a standard web app (SPA + rest api). I'd like to stay as functional as possible. I'm debating between http4s + cats effect, http4s + zio, and zio-http (https://github.com/dream11/zio-http). I'm having a hard time figuring out which stack has the strongest (safest?) future especially with scala 3 out. Cats Effect 3 looks amazing, but so does the zio ecosystem. Thanks for any opinions/advice!

Thanks for the feedback. Full disclosure, I work for the company which open sourced this project.

I haven't been following loom closely, but it appears there are still pieces being put in the Java SE for it and it hasn't been fully delivered.

For instance, in java 19, virtual threads are still in preview[0].

If you wanted to build a web server running on a LTS of Java with loom, you'd have to wait until Sep 2023[1] (though of course you could write code against versions 19+ too).

I think it'd be great to file a feature asking for loom support[2], but do you really think loom is ready to be the foundation of a prod ready web server right now?

Sorry if that sounds like FUD, but I truly don't know. the two projects[3][4] linked in the infoq article are explicitly experimental or demo apps.

That said, I did find this thread of projects that support loom now[5].

0: https://www.infoq.com/news/2022/09/java19-released/

1: https://www.oracle.com/java/technologies/java-se-support-roa...

2: https://github.com/FusionAuth/java-http/issues

3: https://github.com/rokon12/project-loom-slides-and-demo-code

4: https://github.com/nipafx/loom-lab

5: https://twitter.com/nipafx/status/1567448335367151616