Connecting the Dots: The Path from Document Database to Graph Database
summary
Compares Cosmos DB and Neo4j migration with concrete results and methods: an T0–T3 live migration that snapshots, bulk migrates, replays change events and flips a flag to cut over with zero downtime; uses Cosmos change-feed and change-event replay to guarantee consistency and enable rollback; data model shifts from entity-centric to property-centric and replaces monolithic reads with short-circuit boolean Cypher queries and Cypher MERGE idempotent writes; scales across 84,000+ sandboxes and 13,000+ orgs, cutting latency from 800ms to 50ms on average.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 0:47Policy enforcement service overview
- 2:32Cosmos DB limitations
- 4:20Migration to Neo4j benefits
- 6:36Migration strategy and execution
- 9:27Migration results and insights
- 11:55Key takeaways and conclusion
related talks
57mGraphing Your Way Through the Cosmos: Common Data Problems Solved with Graphs
32mMigrating Graph from a (MariaDB & MongoDB) solution to Azure Cosmos DB's Gremlin API
29mSo... Graph Databases
01h 01mFrom SQL to Azure Cosmos DB
01h 02mFrom SQL to Azure Cosmos DB
32mUnderstanding Complexly Connected Data using Graph Databases
54mSay Yes to NoSQL for the .NET SQL Developer
01h 00mWho’s Afraid of Graphs?
