Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Guidelines #58

Open
patriknw opened this issue Nov 9, 2014 · 3 comments
Open

Guidelines #58

patriknw opened this issue Nov 9, 2014 · 3 comments

Comments

@patriknw
Copy link
Owner

patriknw commented Nov 9, 2014

Designing for eventual consistency is difficult, or at least different. We should provide guidelines for various design choices, such as read/write consistency levels.

Let's collect some topics in this issue. Please contribute. Links to blog posts or other related reading/presentations?
@patriknw patriknw mentioned this issue Nov 9, 2014
Closed
@patriknw
Copy link
Owner Author

patriknw commented Nov 9, 2014

Risk of WriteLocal:

JVM crash before the updated value was sent out with gossip means that the update is "lost".

Use case for WriteLocal is when you need low latency and it's acceptable to loose updates if JVM crashes before the data has been spread to other nodes.
For example: web page counter

@sudhakarVuppalapati
Copy link

How to run the project please help

@patriknw
Copy link
Owner Author

patriknw commented Mar 1, 2018

This project has been incorporated on akka/akka as Akka Distributed Data. See docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@patriknw @sudhakarVuppalapati