Akka HTTP alternatives and similar packages
Based on the "HTTP" category.
Alternatively, view Akka HTTP alternatives based on common mentions on social networks and blogs.
-
Spray
DISCONTINUED. A suite of scala libraries for building and consuming RESTful web services on top of Akka: lightweight, asynchronous, non-blocking, actor-based, testable -
requests-scala
A Scala port of the popular Python Requests HTTP client: flexible, intuitive, and straightforward to use. -
Newman
DISCONTINUED. A REST DSL that tries to take the best from Dispatch, Finagle and Apache HttpClient. See here for rationale. -
Tubesocks
A comfortable and fashionable way to have bi-directional conversations with modern web servers. -
jefe
Manages installation, updating, downloading, launching, error reporting, and more for your application.
SaaSHub - Software Alternatives and Reviews
Do you think we are missing an alternative of Akka HTTP or a related project?
README
Akka HTTP
The Akka HTTP modules implement a full server- and client-side HTTP stack on top of akka-actor and akka-stream. It's not a web-framework but rather a more general toolkit for providing and consuming HTTP-based services. While interaction with a browser is of course also in scope it is not the primary focus of Akka HTTP.
Akka HTTP follows a rather open design and many times offers several different API levels for "doing the same thing". You get to pick the API level of abstraction that is most suitable for your application. This means that, if you have trouble achieving something using a high-level API, there's a good chance that you can get it done with a low-level API, which offers more flexibility but might require you to write more application code.
Learn more at akka.io.
Documentation
The documentation is available at doc.akka.io, for Scala and Java.
Community
You can join these groups and chats to discuss and ask Akka related questions:
- Forums: discuss.akka.io
- Chat room about using Akka HTTP:
- Q&A:
- Issue tracker: (Please use the issue tracker for bugs and reasonable feature requests. Please ask usage questions on the other channels.)
All of our forums, chat rooms, and issue trackers are governed by our Code Of Conduct.
In addition to that, you may enjoy following:
- The news section of the page, which is updated whenever a new version is released
- The Akka Team Blog
- @akkateam on Twitter
- Projects built with Akka HTTP:
Contributing
Contributions are very welcome!
If you see an issue that you'd like to see fixed, the best way to make it happen is to help out by submitting a pull request. For ideas of where to contribute, tickets marked as "help wanted" are a good starting point.
Refer to the [CONTRIBUTING.md](CONTRIBUTING.md) file for more details about the workflow, and general hints on how to prepare your pull request. You can also ask for clarifications or guidance in GitHub issues directly, or in the akka/dev chat if a more real-time communication would be of benefit.
A chat room is available for all questions related to developing and contributing to Akka:
Maintenance
This project is maintained by Lightbend's core Akka Team as well as the extended Akka HTTP Team, consisting of excellent and experienced developers who have shown their dedication and knowledge about HTTP and the codebase. This team may grow dynamically, and it is possible to propose new members to it.
Joining the extended team in such form gives you, in addition to street-cred, of course committer rights to this repository as well as higher impact onto the roadmap of the project. Come and join us!
License
Akka HTTP is licensed under the Business Source License 1.1, see LICENSE.txt.
*Note that all licence references and agreements mentioned in the Akka HTTP README section above
are relevant to that project's source code only.