Video and slides synchronized, mp3 and slide download available at URL http://bit.ly/2nSKaat.
Jim Webber explores the new Causal clustering architecture for Neo4j, showing that, despite the mixture of consensus protocols and asynchronous replication, Neo4j allows users to read their own writes straightforwardly, and discusses why this is such a difficult achievement in distributed systems. Filmed at qconlondon.com.
Jim Webber is Chief Scientist with Neo Technology, the company behind the popular open source graph database Neo4j. He works on R&D for highly scalable graph databases and writes open source software. He has written two books on integration and distributed systems: “Developing Enterprise Web Services” and “REST in Practice”. His latest book is “Graph Databases” which focuses on the Neo4j database.
08448380779 Call Girls In Civil Lines Women Seeking Men
Causal Consistency for Large Neo4j Clusters
1. Causal Consistency For Large Neo4j Clusters
Jim Webber
Chief Scientist, Neo4j
QCon London
2. InfoQ.com: News & Community Site
Watch the video with slide
synchronization on InfoQ.com!
https://www.infoq.com/presentations
/causal-clustering-neo4j
• Over 1,000,000 software developers, architects and CTOs read the site world-
wide every month
• 250,000 senior developers subscribe to our weekly newsletter
• Published in 4 languages (English, Chinese, Japanese and Brazilian
Portuguese)
• Post content from our QCon conferences
• 2 dedicated podcast channels: The InfoQ Podcast, with a focus on
Architecture and The Engineering Culture Podcast, with a focus on building
• 96 deep dives on innovative topics packed as downloadable emags and
minibooks
• Over 40 new content items per week
3. Purpose of QCon
- to empower software development by facilitating the spread of
knowledge and innovation
Strategy
- practitioner-driven conference designed for YOU: influencers of
change and innovation in your teams
- speakers and topics driving the evolution and innovation
- connecting and catalyzing the influencers and innovators
Highlights
- attended by more than 12,000 delegates since 2007
- held in 9 cities worldwide
Presented at QCon London
www.qconlondon.com
40. Raft in a Nutshell
• Raft keeps logs tied together (geddit?)
• Logs contain entries for both the database and the cluster membership
• Entries are appended and subsequently committed if a simple majority agree
• Implication: majority agree with the log as proposed
• Anyone can call an election: highest term (logical clock) wins, followed by highest committed,
followed by highest appended.
• Appended, but not committed, entries can be truncated, but this is safe (translates as transaction
aborted)
https://github.com/ongardie/raftscope
63. Cluster members slightly “ahead” or “behind” of each other
0 1 2 3 4 5 6 7 8 9 10
11
0 1 2 3 4 5 6 7 8 9 10
0 1 2 3 4 5 6 7 8 9 10
0 1 2 3 4 5 6 7 8 9 10
0 1 2 3 4 5 6 7 8 9 10
If I query this server I
won’t see the updates
from transaction .
If I query this server,
I’ll see all updates
from all committed
transactions
11
11
83. Bookmark
Session token
String (for portability)
Opaque to application
Represents ultimate user’s most recent view
of the graph
More capabilities to come