zio-http VS zio-protoquill

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!

There is: https://github.com/zio/zio-protoquill

Among Scala 3-only macro codebases is proto-quill (Quill for Scala 3). Other than that most libraries will be cross-compiled Scala 2 and Scala 3 because they have to cater to both long-time Scala 2 users as well as those who already migrated.

Proto Quill, a query DSL similar-ish to Slick, is certainly the poster child of what's possible with Scala 3 macros.

I know that libraries like Scodec and shapeless were rewritten practically from scratch for Scala 3, taking advantage of the next syntax and internals, as well as protoquill - a Scala 3 implementation of Quill.

I am a Scala engineer and have upstreamed a lot of open source projects to do this, (i.e. see https://github.com/getquill/protoquill/pull/17). Basically its a github action that runs concurrently to the main build, this has the following advantages

I've been refreshing https://github.com/getquill/protoquill nearly every day!