Docs: link to videos (#29799)
This commit is contained in:
parent
abfd699985
commit
a57742f31b
2 changed files with 3 additions and 2 deletions
|
|
@ -196,7 +196,8 @@ in one rebalance round. The lower result of `rebalance-relative-limit` and `reba
|
|||
|
||||
An alternative allocation strategy is the @apidoc[ExternalShardAllocationStrategy] which allows
|
||||
explicit control over where shards are allocated via the @apidoc[ExternalShardAllocation] extension.
|
||||
This can be used, for example, to match up Kafka Partition consumption with shard locations.
|
||||
|
||||
This can be used, for example, to match up Kafka Partition consumption with shard locations. The video [How to co-locate Kafka Partitions with Akka Cluster Shards](https://akka.io/blog/news/2020/03/18/akka-sharding-kafka-video) explains a setup for it. Alpakka Kafka provides [an extension for Akka Cluster Sharding](https://doc.akka.io/docs/alpakka-kafka/current/cluster-sharding.html).
|
||||
|
||||
To use it set it as the allocation strategy on your `Entity`:
|
||||
|
||||
|
|
|
|||
|
|
@ -38,7 +38,7 @@ to handle this.
|
|||
To be able to use Replicated Event Sourcing the journal and snapshot store used is required to have specific support for the metadata that the replication needs (see @ref[Journal Support](#journal-support)).
|
||||
|
||||
The [Replicated Event Sourcing video](https://akka.io/blog/news/2020/09/09/replicated-event-sourcing-video)
|
||||
is a good starting point describing the use cases and motivation for when to use Replicated Event Sourcing.
|
||||
is a good starting point describing the use cases and motivation for when to use Replicated Event Sourcing. The second part, [Replicated Event Sourcing data modelling](https://akka.io/blog/news/2020/10/22/replicated-event-sourcing-data-modelling) guides you to find a suitable model for your use-case.
|
||||
|
||||
## Relaxing the single-writer principle for availability
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue