0.8.0
🔈 Announcing Coerce 0.8.0
- Feature flags: "remote", "persistence", "metrics", "sharding", "api"
ActorSystem
memory usage improvements, now it is just a wrapper over anArc<ActorSystemCore>
, allowing for much cheaper cloning.RemoteActorSystem
can now be cleanly shutdown- Cluster node termination fixes and improvements, nodes will now emit a message to peers upon system termination and leaders should be re-allocated immediately, which will help improve cluster reliability as a whole
- Multiple persistence backends can now be configured based on the actor's type
- Redis persistence journal provider has been refactored and is now backed by its own actor
- New Kubernetes discovery provider, you can now automatically discover peers hosted in Kubernetes, based on a configurable pod-selection label
- Cluster sharding chat example application now uses protobuf for serialisation throughout
- Updated the cluster sharding chat example application with kubernetes deployment manifests (kustomize)
- Added specific unit test for cluster heartbeat / state consistency after losing the leader node
- Added unit test for shard rebalancing after losing the leader node and more
- Several actor persistence resilience improvements
- Actor describe functionality, ability to examine the actor hierarchy via
Describe
message or the HTTP API - Ability to add tags to actors, which can be retrieved via the describe functionality
- Error propagation and handling improvements
- Dependency updates
So much more!
Full Changelog: 0.7.0...0.8.0