akka/akka-core

PubSub optimization publishing across data centers

Open

#23,247 opened on Jun 28, 2017

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Scala (3,547 forks)batch import
1 - triagedhelp wantedt:cluster:dc

Repository metrics

Stars
 (13,277 stars)
PR merge metrics
 (Avg merge 8d 19h) (10 merged PRs in 30d)

Description

When the cluster is divided in multi-dc and we Publish a message to all subscribers, it might be a neat optimization to send the message only once to each other DC, and make sure it gets distributed correctly there.

Contributor guide

Research direction
Investigate Akka's PubSub internals to understand how messages are currently distributed across data centers. Propose an optimization to send a single message per remote data center and let that data center distribute it locally. Look for existing multi dc cluster support and serialization considerations.
Tech stack
scala
Domain
distributed systemsbackend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
ScalaAkka
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30