164387a89e
* Guarantee no sneaky type puts more teams in the role list * Leader per team and initial tests * MiMa filters * Second iteration (not working though) * Verbose gossip logging etc. * Gossip to team-nodes even if there is inter-team unreachability * More work ... * Marking removed nodes with tombstones in Gossip * More test coverage for Gossip.remove * Bug failing other multi-node tests squashed * Multi-node test for team-split * Review fixes - only prune tombstones on leader ticks * Clean code is happy code. * All I want is for MiMa to be my friend * These constants are internal * Making the formatting gods happy * I used the wrong reachability for ignoring gossip :/ * Still hadn't quite gotten how reachability was supposed to work * Review feedback applied * Cross-team downing should still work * Actually prune tombstones in the prune tombstones method ... * Another round against reachability. Reachability leading with 15 - 2 so far. |
||
|---|---|---|
| akka-actor | ||
| akka-actor-tests | ||
| akka-agent | ||
| akka-bench-jmh | ||
| akka-camel | ||
| akka-cluster | ||
| akka-cluster-metrics | ||
| akka-cluster-sharding | ||
| akka-cluster-tools | ||
| akka-contrib | ||
| akka-distributed-data | ||
| akka-docs | ||
| akka-multi-node-testkit | ||
| akka-osgi | ||
| akka-persistence | ||
| akka-persistence-query | ||
| akka-persistence-shared | ||
| akka-persistence-tck | ||
| akka-protobuf | ||
| akka-remote | ||
| akka-remote-tests | ||
| akka-slf4j | ||
| akka-ssl-config/src/main/scala/com/lightbend/sslconfig/akka | ||
| akka-stream | ||
| akka-stream-testkit | ||
| akka-stream-tests | ||
| akka-stream-tests-tck | ||
| akka-testkit | ||
| akka-typed | ||
| akka-typed-testkit | ||
| akka-typed-tests | ||
| project | ||
| scripts | ||
| src/main/ls | ||
| .gitignore | ||
| .java-version | ||
| build.sbt | ||
| CONTRIBUTING.md | ||
| COPYING.protobuf | ||
| LICENSE | ||
| README.md | ||
Akka
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.
Reference Documentation
The reference 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:
- Mailing list:
- Chat room about using Akka:
- Issue tracker:
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
- Questions tagged #akka on StackOverflow
- Projects built with Akka:
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 implementing it.
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:
License
Akka is Open Source and available under the Apache 2 License.