Project Name | Stars | Downloads | Repos Using This | Packages Using This | Most Recent Commit | Total Releases | Latest Release | Open Issues | License | Language |
---|---|---|---|---|---|---|---|---|---|---|
Akka | 12,696 | 34 | 168 | 19 hours ago | 77 | September 09, 2022 | 911 | other | Scala | |
Build highly concurrent, distributed, and resilient message-driven applications on the JVM | ||||||||||
Elixirbooks | 1,173 | 10 months ago | other | |||||||
List of Elixir books | ||||||||||
Dbtester | 221 | 3 years ago | May 24, 2021 | 4 | apache-2.0 | Go | ||||
Distributed database benchmark tester | ||||||||||
Tractor | 210 | 2 | 17 days ago | 34 | August 03, 2022 | 128 | agpl-3.0 | Python | ||
structured concurrent, Python parallelism | ||||||||||
Wukong | 107 | 3 years ago | 2 | apache-2.0 | C++ | |||||
A graph-based distributed in-memory store that leverages efficient graph exploration to provide highly concurrent and low-latency queries over big linked data | ||||||||||
Storage | 79 | 5 years ago | 1 | August 17, 2017 | 3 | mit | JavaScript | |||
Concurrent, implicit persistence for node.js | ||||||||||
Clock | 28 | 4 years ago | 3 | October 25, 2019 | mit | Rust | ||||
Logical clocks implementation in Rust | ||||||||||
Distributed | 21 | 5 years ago | 3 | December 20, 2017 | mit | Elixir | ||||
Distributed is a wrapper module that helps developers to make distributed, scaled, replicated and fault-tolerant (with takeover ability) master-slave systems. | ||||||||||
Spider | 15 | a year ago | 5 | mit | Java | |||||
Automated data race detection from a distributed trace via SMT constraint solving | ||||||||||
Fuego Cache | 13 | 2 years ago | 3 | December 22, 2020 | 10 | apache-2.0 | Go | |||
Fuego cache is a concurrent hashed key-value pair service written 100% in Golang. A high-speed cache service with HTTP and plain TCP and CLI interfaces with persistence in disk. Easy-to-use & easy-to-deploy cache service totally free. PRs are welcome folks. |
We believe that writing correct concurrent & distributed, resilient and elastic applications is too hard. Most of the time it's because we are using the wrong tools and the wrong level of abstraction.
Akka is here to change that.
Using the Actor Model we raise the abstraction level and provide a better platform to build correct concurrent and scalable applications. This model is a perfect match for the principles laid out in the Reactive Manifesto.
For resilience, we adopt the "Let it crash" model which the telecom industry has used with great success to build applications that self-heal and systems that never stop.
Actors also provide the abstraction for transparent distribution and the basis for truly scalable and fault-tolerant applications.
Learn more at akka.io.
The reference documentation is available at doc.akka.io, for Scala and Java.
You can join these groups and chats to discuss and ask Akka related questions:
In addition to that, you may enjoy following:
Contributions are very welcome!
If you see an issue that you'd like to see fixed, or want to shape out some ideas, the best way to make it happen is to help out by submitting a pull request implementing it. We welcome contributions from all, even you are not yet familiar with this project, We are happy to get you started, and will guide you through the process once you've submitted your PR.
Refer to the 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:
Akka is licensed under the Business Source License 1.1, see LICENSE.