Akka.Delivery is a reliable delivery system that leverages built-in actors, serialization, and persistence to help guarantee that all messages sent from one producer to one consumer will be delivered, in-order, even across process restarts / actor restarts / network outages.
Akka.Delivery's functionality is divded across four libraries:
Akka - defines the base definitions for all messages, the ProducerController type, and the ConsumerController type;
Akka.Cluster - contains the serialization definitions for Akka.Delivery;
Akka.Persistence - contains the EventSourcedProducerQueue implementation, an optional feature that can be used to make the ProducerController's outbound delivery queue persisted to the Akka.Persistence Journal and SnapshotStore; and
Akka.Cluster.Sharding - contains the definitions for the ShardingProducerController and ShardingConsumerController.
We've documented how these features work in the following two detailed articles official website:
Akka.Delivery is a reliable delivery system that leverages built-in actors, serialization, and persistence to help guarantee that all messages sent from one producer to one consumer will be delivered, in-order, even across process restarts / actor restarts / network outages.
Akka.Delivery's functionality is divded across four libraries:
Akka - defines the base definitions for all messages, the ProducerController type, and the ConsumerController type;
Akka.Cluster - contains the serialization definitions for Akka.Delivery;
Akka.Persistence - contains the EventSourcedProducerQueue implementation, an optional feature that can be used to make the ProducerController's outbound delivery queue persisted to the Akka.Persistence Journal and SnapshotStore; and
Akka.Cluster.Sharding - contains the definitions for the ShardingProducerController and ShardingConsumerController.
We've documented how these features work in the following two detailed articles official website:
Akka.Delivery is a reliable delivery system that leverages built-in actors, serialization, and persistence to help guarantee that all messages sent from one producer to one consumer will be delivered, in-order, even across process restarts / actor restarts / network outages.
Akka.Delivery's functionality is divded across four libraries:
Akka - defines the base definitions for all messages, the ProducerController type, and the ConsumerController type;
Akka.Cluster - contains the serialization definitions for Akka.Delivery;
Akka.Persistence - contains the EventSourcedProducerQueue implementation, an optional feature that can be used to make the ProducerController's outbound delivery queue persisted to the Akka.Persistence Journal and SnapshotStore; and
Akka.Cluster.Sharding - contains the definitions for the ShardingProducerController and ShardingConsumerController.
We've documented how these features work in the following two detailed articles official website:
Akka.Delivery is a reliable delivery system that leverages built-in actors, serialization, and persistence to help guarantee that all messages sent from one producer to one consumer will be delivered, in-order, even across process restarts / actor restarts / network outages.
Akka.Delivery's functionality is divded across four libraries:
Akka - defines the base definitions for all messages, the ProducerController type, and the ConsumerController type;
Akka.Cluster - contains the serialization definitions for Akka.Delivery;
Akka.Persistence - contains the EventSourcedProducerQueue implementation, an optional feature that can be used to make the ProducerController's outbound delivery queue persisted to the Akka.Persistence Journal and SnapshotStore; and
Akka.Cluster.Sharding - contains the definitions for the ShardingProducerController and ShardingConsumerController.
We've documented how these features work in the following two detailed articles official website:
Akka.Delivery is a reliable delivery system that leverages built-in actors, serialization, and persistence to help guarantee that all messages sent from one producer to one consumer will be delivered, in-order, even across process restarts / actor restarts / network outages.
Akka.Delivery's functionality is divded across four libraries:
Akka - defines the base definitions for all messages, the ProducerController type, and the ConsumerController type;
Akka.Cluster - contains the serialization definitions for Akka.Delivery;
Akka.Persistence - contains the EventSourcedProducerQueue implementation, an optional feature that can be used to make the ProducerController's outbound delivery queue persisted to the Akka.Persistence Journal and SnapshotStore; and
Akka.Cluster.Sharding - contains the definitions for the ShardingProducerController and ShardingConsumerController.
We've documented how these features work in the following two detailed articles official website:
Akka.Delivery is a reliable delivery system that leverages built-in actors, serialization, and persistence to help guarantee that all messages sent from one producer to one consumer will be delivered, in-order, even across process restarts / actor restarts / network outages.
Akka.Delivery's functionality is divded across four libraries:
Akka - defines the base definitions for all messages, the ProducerController type, and the ConsumerController type;
Akka.Cluster - contains the serialization definitions for Akka.Delivery;
Akka.Persistence - contains the EventSourcedProducerQueue implementation, an optional feature that can be used to make the ProducerController's outbound delivery queue persisted to the Akka.Persistence Journal and SnapshotStore; and
Akka.Cluster.Sharding - contains the definitions for the ShardingProducerController and ShardingConsumerController.
We've documented how these features work in the following two detailed articles official website:
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Bumps
AkkaVersion
from 1.5.6 to 1.5.8. UpdatesAkka
from 1.5.6 to 1.5.8Release notes
Sourced from Akka's releases.
... (truncated)
Changelog
Sourced from Akka's changelog.
Commits
b6d1ce3
added v1.5.8 release notes (#6795)5fa8ef4
Added Source/Flow Setup operator (#6788)74c59c5
Bump Microsoft.NET.Test.Sdk from 17.6.0 to 17.6.2 (#6785)6de2171
Bump Verify.Xunit from 20.3.0 to 20.3.2 (#6786)4e23091
Bump Microsoft.Data.SQLite from 7.0.5 to 7.0.7 (#6791)2b9c059
Bump NUnit3TestAdapter from 4.4.2 to 4.5.0 (#6779)2873951
docs: fix wrong link syntax in docs/articles/configuration/config.md (#6782)e014825
remove some state machine (#6787)c3e03a8
Bump Google.Protobuf from 3.23.1 to 3.23.2 (#6777)0efdc87
Bump Verify.Xunit from 20.1.1 to 20.3.0 (#6776)Updates
Akka.Serialization.Hyperion
from 1.5.6 to 1.5.8Release notes
Sourced from Akka.Serialization.Hyperion's releases.
... (truncated)
Changelog
Sourced from Akka.Serialization.Hyperion's changelog.
Commits
b6d1ce3
added v1.5.8 release notes (#6795)5fa8ef4
Added Source/Flow Setup operator (#6788)74c59c5
Bump Microsoft.NET.Test.Sdk from 17.6.0 to 17.6.2 (#6785)6de2171
Bump Verify.Xunit from 20.3.0 to 20.3.2 (#6786)4e23091
Bump Microsoft.Data.SQLite from 7.0.5 to 7.0.7 (#6791)2b9c059
Bump NUnit3TestAdapter from 4.4.2 to 4.5.0 (#6779)2873951
docs: fix wrong link syntax in docs/articles/configuration/config.md (#6782)e014825
remove some state machine (#6787)c3e03a8
Bump Google.Protobuf from 3.23.1 to 3.23.2 (#6777)0efdc87
Bump Verify.Xunit from 20.1.1 to 20.3.0 (#6776)Updates
Akka.TestKit.Xunit2
from 1.5.6 to 1.5.8Release notes
Sourced from Akka.TestKit.Xunit2's releases.
... (truncated)
Changelog
Sourced from Akka.TestKit.Xunit2's changelog.
Commits
b6d1ce3
added v1.5.8 release notes (#6795)5fa8ef4
Added Source/Flow Setup operator (#6788)74c59c5
Bump Microsoft.NET.Test.Sdk from 17.6.0 to 17.6.2 (#6785)6de2171
Bump Verify.Xunit from 20.3.0 to 20.3.2 (#6786)4e23091
Bump Microsoft.Data.SQLite from 7.0.5 to 7.0.7 (#6791)2b9c059
Bump NUnit3TestAdapter from 4.4.2 to 4.5.0 (#6779)2873951
docs: fix wrong link syntax in docs/articles/configuration/config.md (#6782)e014825
remove some state machine (#6787)c3e03a8
Bump Google.Protobuf from 3.23.1 to 3.23.2 (#6777)0efdc87
Bump Verify.Xunit from 20.1.1 to 20.3.0 (#6776)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)