kmq
Kafka-based message queue (by softwaremill)
Play WS
Standalone Play WS, an async HTTP client with fluent API (by playframework)
| kmq | Play WS | |
|---|---|---|
| 1 | 2 | |
| 322 | 221 | |
| 0.6% | 0.5% | |
| 0.0 | 8.2 | |
| 9 days ago | 8 days ago | |
| Scala | Scala | |
| Apache License 2.0 | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
kmq
Posts with mentions or reviews of kmq.
We have used some of these posts to build our list of alternatives
and similar projects.
-
FedNow Is Live
thanks for the reply!
I'm aware that Kafka is low-level (and that there is kmq, which tries to implement a message queue on top of it https://github.com/softwaremill/kmq/ ), but the exactly-once semantics seems isomorphic to having the sender and the receiver doing a 2 phase commit using the log.
what are MQ's guarantees? how are they implemented?
Play WS
Posts with mentions or reviews of Play WS.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-09-06.
-
Code in jar dependency is packed as java code and can not be used as normal Scala dependency
Take a look at https://github.com/playframework/play-ws build.sbt. it is a scala lib built with sbt-assembly to shade dependencies and avoid binary incompatibility. That is the only reason to build a lib with sbt-assembly.
-
Scala or Go: Who Wore It Better?
In this example, the code uses Play WS Standalone as a REST client to fetch JSON containing a UUID. Play WS has an asynchronous, non-blocking API based on Future, so you need to provide an ExecutionContext via Akka. That's all the boilerplate at the beginning of this example. Sometimes it will be done for you as when you use Play WS in the context of Play Framework. Nonetheless, you should be aware it has to happen somewhere.
What are some alternatives?
When comparing kmq and Play WS you can also consider the following projects:
Reactor-Scala-Extensions - A scala extension for Project Reactor's Flux and Mono
unirest-java - Unirest in Java: Simplified, lightweight HTTP client library.