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)
dependabot[bot]
commented
1 year ago
Bumps
AkkaVersionfrom 1.5.6 to 1.5.7. UpdatesAkkafrom 1.5.6 to 1.5.7Release notes
Sourced from Akka's releases.
... (truncated)
Changelog
Sourced from Akka's changelog.
Commits
c11e5c6added v1.5.7 release notes (#6767)d7304f4Revert "MakeHandleActorTaskSchedulerMessagemethodprotected virtual(#6...c514fd1discard some parameters (#6751)88be1fc[CS0618]GraphInterpreterSpecKit(#6697)1345e58MakeHandleActorTaskSchedulerMessagemethodprotected virtual(#6763)3e1b8e5[Docs] Akka.Delivery Documentation (#6757)a8aeadfUpgrade Akka.MultiNodeTestRunner to 1.5.6 (#6764)49bc347Bump Microsoft.NET.Test.Sdk from 17.5.0 to 17.6.0 (#6762)a3eb0ddUpdate documentation-guidelines.mdfe2405d[CS0618][Obsolete] PerserveCreateProducer(#6673)Updates
Akka.Serialization.Hyperionfrom 1.5.6 to 1.5.7Release notes
Sourced from Akka.Serialization.Hyperion's releases.
... (truncated)
Changelog
Sourced from Akka.Serialization.Hyperion's changelog.
Commits
c11e5c6added v1.5.7 release notes (#6767)d7304f4Revert "MakeHandleActorTaskSchedulerMessagemethodprotected virtual(#6...c514fd1discard some parameters (#6751)88be1fc[CS0618]GraphInterpreterSpecKit(#6697)1345e58MakeHandleActorTaskSchedulerMessagemethodprotected virtual(#6763)3e1b8e5[Docs] Akka.Delivery Documentation (#6757)a8aeadfUpgrade Akka.MultiNodeTestRunner to 1.5.6 (#6764)49bc347Bump Microsoft.NET.Test.Sdk from 17.5.0 to 17.6.0 (#6762)a3eb0ddUpdate documentation-guidelines.mdfe2405d[CS0618][Obsolete] PerserveCreateProducer(#6673)Updates
Akka.TestKit.Xunit2from 1.5.6 to 1.5.7Release notes
Sourced from Akka.TestKit.Xunit2's releases.
... (truncated)
Changelog
Sourced from Akka.TestKit.Xunit2's changelog.
Commits
c11e5c6added v1.5.7 release notes (#6767)d7304f4Revert "MakeHandleActorTaskSchedulerMessagemethodprotected virtual(#6...c514fd1discard some parameters (#6751)88be1fc[CS0618]GraphInterpreterSpecKit(#6697)1345e58MakeHandleActorTaskSchedulerMessagemethodprotected virtual(#6763)3e1b8e5[Docs] Akka.Delivery Documentation (#6757)a8aeadfUpgrade Akka.MultiNodeTestRunner to 1.5.6 (#6764)49bc347Bump Microsoft.NET.Test.Sdk from 17.5.0 to 17.6.0 (#6762)a3eb0ddUpdate documentation-guidelines.mdfe2405d[CS0618][Obsolete] PerserveCreateProducer(#6673)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)