a2e5b3f8a4
* I think it originated from channels, or some idea that the sender should be revived (as good as possible) during replay, but that is pretty useless * It must still be in PersistentRepr for remote serialization * I didn't want to change to the built in sender when looping to the journal because keeping it together with the message makes it easier to do batching (queueing) * adjust tck |
||
|---|---|---|
| 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-docs | ||
| akka-kernel | ||
| akka-multi-node-testkit | ||
| akka-osgi | ||
| akka-persistence | ||
| akka-persistence-tck | ||
| akka-remote | ||
| akka-remote-tests | ||
| akka-samples | ||
| akka-slf4j | ||
| akka-stream/src | ||
| akka-testkit | ||
| akka-typed | ||
| atmos/src/main/resources | ||
| project | ||
| scripts | ||
| src/main/ls | ||
| .gitignore | ||
| build.sbt | ||
| CONTRIBUTING.md | ||
| 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.
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.
Akka is Open Source and available under the Apache 2 License.
Learn more at akka.io. Join the akka-user mailing list. Follow @akkateam on twitter.
