cable
zio-http
cable | zio-http | |
---|---|---|
4 | 8 | |
34 | 736 | |
- | 1.1% | |
0.0 | 9.4 | |
about 3 years ago | 4 days ago | |
Scala | Scala | |
- | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
cable
-
A ssh library that is functional and practical
Cable is coming to stable now as v0.2.0, with both the dynamic and static constructing DSL, the result types, the APIs now should be relatively stable. Had done more tests. Added some static & dynamic constructing DSL for easier usage. Added more examples on fact-chaining on both dynamic way and static way of tasks composing.
zio-http
-
Creating a CLI app with scala and Graal VM: should I switch to Rust?
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 is scala's modern Web API framework?
-
Show HN: Open-source non-blocking NIO Java HTTP Server
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
-
Akka Fork FUD
Yep! https://github.com/zio/zio-http
-
zio-http, any experiences to share
I was looking at HTTP frameworks for Scala. I found zio-http, https://zio.github.io/zio-http/. Has anyone tried this framework?
- How is scala as microservices-based backend for web service?
-
A library like Express.js?
https://github.com/dream11/zio-http very simple and super performant, dead easy to abstract over routes to make a router
-
ZIO vs. Cats Effect for api
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!
What are some alternatives?
zio-json - Fast, secure JSON library with tight ZIO integration.
Http4s - A minimal, idiomatic Scala interface for HTTP
DIStage - Productivity-oriented collection of lightweight fancy stuff for Scala toolchain
FrameworkBenchmarks - Source for the TechEmpower Framework Benchmarks project
tapir - Declarative, type-safe web endpoints library
Vert.x - Vert.x is a tool-kit for building reactive applications on the JVM
zio-saga - Purely Functional Transaction Management In Scala With ZIO
vertx-lang-scala - Vert.x for Scala
cask - Cask: a Scala HTTP micro-framework
zio-protoquill - Quill for Scala 3
ocpp - Open Charge Point Protocol
libreforge - Self-hosted git and fuller service built from microservices