H2scala
| Project Name | Stars | Downloads | Repos Using This | Packages Using This | Most Recent Commit | Total Releases | Latest Release | Open Issues | License | Language |
|---|---|---|---|---|---|---|---|---|---|---|
| Alpakka Kafka | 1,398 | 8 | 131 | 7 days ago | 37 | July 26, 2021 | 110 | other | Scala | |
| Alpakka Kafka connector - Alpakka is a Reactive Enterprise Integration library for Java and Scala, based on Reactive Streams and Akka. | ||||||||||
| Squbs | 1,381 | 6 | a year ago | 12 | January 18, 2021 | 69 | apache-2.0 | Scala | ||
| Akka Streams & Akka HTTP for Large-Scale Production Deployments | ||||||||||
| Alpakka | 1,249 | 2 | 112 | 9 days ago | 45 | November 30, 2021 | 220 | other | Scala | |
| Alpakka is a Reactive Enterprise Integration library for Java and Scala, based on Reactive Streams and Akka. | ||||||||||
| Real_world_scala | 621 | 5 years ago | 1 | HTML | ||||||
| an introduction book on real world's scala, including its main stream frameworks and MOMs... | ||||||||||
| Akka.js | 456 | 11 | 2 years ago | 22 | March 16, 2020 | 7 | Scala | |||
| Akka, for Scala.js | ||||||||||
| Akka Grpc | 419 | 4 | 17 | 2 days ago | 40 | September 26, 2022 | 165 | other | Scala | |
| Akka gRPC | ||||||||||
| Akka Streams Example | 362 | 5 months ago | 2 | Scala | ||||||
| Cloudflow | 323 | 7 | 16 days ago | 604 | October 03, 2022 | 119 | apache-2.0 | Scala | ||
| Cloudflow enables users to quickly develop, orchestrate, and operate distributed streaming applications on Kubernetes. | ||||||||||
| Reactive | 300 | 5 months ago | 4 | Java | ||||||
| Reactive: Examples of the most famous reactive libraries that you can find in the market. | ||||||||||
| Akka Analytics | 281 | 7 years ago | apache-2.0 | Scala | ||||||
| Large-scale event processing with Akka Persistence and Apache Spark | ||||||||||
HTTP/2 Server implementation is Scala and Akka Streams
This implements the basics of an HTTP/2 server using Akka Streams for all the data flow.
All the build is handled by SBT, and using it should be enough to compile and start testing.
Any actual programs that run the server must start with the Jetty ALPN JAR in it's bootclasspath. Since there are not supported plain-text protocols this wiill cause issue immediately if not taken care of.
Also, it's necessary to have a keystore set-up, even if with a temporary replacement. Tutorials on how to achieve that are a available in many places.
One simple example application server is included that just serves files in the local directory, which can be run with
sbt examples/run
The default application instance can also be debugged using the :debug configuration.
