Netflix's Real-Time Distributed Graph, Part 2 — Building a Scalable Storage Layer
Artikel konnten nicht hinzugefügt werden
Der Titel konnte nicht zum Warenkorb hinzugefügt werden.
Der Titel konnte nicht zum Merkzettel hinzugefügt werden.
„Von Wunschzettel entfernen“ fehlgeschlagen.
„Podcast folgen“ fehlgeschlagen
„Podcast nicht mehr folgen“ fehlgeschlagen
Netflix's Real-Time Distributed Graph, Part 2 — Building a Scalable Storage Layer
-
Gesprochen von:
-
Von:
Why Netflix skipped native graph databases (Neo4j, Neptune) for its Real-Time Distributed Graph and built on KVDAL — a key-value abstraction over Apache Cassandra — instead. Jordan and Riley cover the record/item mapping that makes a key-value store hold a graph (nodes as property records, edges as adjacency lists), the per-type namespace model for independent scaling, and the scale: 8 billion nodes, 150+ billion edges, 2M reads/sec and 6M writes/sec at single-digit-millisecond latency across 2,400 EC2 instances.
Source: How and Why Netflix Built a Real-Time Distributed Graph, Part 2: Building a Scalable Storage Layer — Netflix Tech Blog, Nov 14 2025 — https://netflixtechblog.medium.com/how-and-why-netflix-built-a-real-time-distributed-graph-part-2-building-a-scalable-storage-layer-ff4a8dbd3d1f
This is commentary/summary in the hosts' own words, not a reproduction of the article.