0c0e3c5efd
* outbound compression is now immutable, by simply using CompressionTable[ActorRef] and CompressionTable[String] * immutable outbound compression will make it possible to use them from multiple Encoder instances, when we add several lanes for parallel serialization * outbound compression tables not shared via AssociationState * the advertised tables are sent to the Encoder stage via async callback, no need to reference the tables in other places than the Encoder stage, no more races via shared mutable state * when outbound stream is started or restarted it can start out without compression, until next advertisement is received * ensure outbound compression is cleared before handshake is signaled complete |
||
|---|---|---|
| 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-http | ||
| akka-http-core | ||
| akka-http-marshallers-java/akka-http-jackson | ||
| akka-http-marshallers-scala | ||
| akka-http-testkit | ||
| akka-http-tests | ||
| akka-kernel | ||
| akka-multi-node-testkit | ||
| akka-osgi | ||
| akka-parsing | ||
| akka-persistence | ||
| akka-persistence-query | ||
| akka-persistence-shared | ||
| akka-persistence-tck | ||
| akka-protobuf | ||
| akka-remote | ||
| akka-remote-tests | ||
| akka-samples | ||
| akka-slf4j | ||
| akka-stream | ||
| akka-stream-testkit | ||
| akka-stream-tests | ||
| akka-stream-tests-tck | ||
| akka-testkit | ||
| akka-typed | ||
| 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
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 PullRequest implementing it.
Refer to the CONTRIBUTING.md file for more details about the workflow, and general hints how to prepare your pull request. You can also chat 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.