Graph Database Internals:

In this episode I talk to Michael Hunger from Neo4j about Graph Database Internals (Neo4J)
Chapters:
0:00 Introduction and historical context
20:51 Data Modelling
25:16 Problem with SQL for Graph Model
26:21 Cypher - Query Language
28:23 Write Path
31:36 Neo4J Storage Layer
33:51 Graph API on top of Relational Model vs Native Graph Databases
37:05 Create Node Relationships
40:42 What makes Graph Database's performance better?
46:00 Partitioning Strategy
53:20 Read path
59:27 Schema Migration
01:04:41 Graph database use cases
===============================================================================
For discount on the below courses:
Appsync: appsyncmasterclass.com/?affil...
Testing serverless: testserverlessapps.com/?affil...
Production-Ready Serverless: productionreadyserverless.com...
Use the button, Add Discount and enter "geeknarrator" discount code to get 20% discount.
===============================================================================
Follow me on Linkedin and Twitter: / kaivalyaapte and / thegeeknarrator
If you like this episode, please hit the like button and share it with your network.
Also please subscribe if you haven't yet.
Database internals series: • Write-ahead-logging
Popular playlists:
Realtime streaming systems: • Realtime Streaming Sys...
Software Engineering: • Software Engineering
Distributed systems and databases: • Distributed Systems an...
Modern databases: • Modern Databases
Stay Curios! Keep Learning!
Cheers,
The GeekNarrator

Пікірлер: 5

  • @nosh3019
    @nosh30195 ай бұрын

    Been looking for high quality and deep engineering content for senior+ like this one. Thanks a bunch and happy holidays! 🎉

  • @TheGeekNarrator

    @TheGeekNarrator

    5 ай бұрын

    Thanks a lot 🙏🏻❤️

  • @richi12345678910
    @richi123456789107 ай бұрын

    What a brilliant channel. Subscribed. Great stuff!

  • @TheGeekNarrator

    @TheGeekNarrator

    7 ай бұрын

    Thank you so much 🙏🏻😀

  • @kellymoses8566
    @kellymoses85667 ай бұрын

    Graph databases are just fundamentally more enjoyable to work with than relational databases. I always found it strange that Relational databases do not have explicit relationships, only implied relationships via foreign keys. And there is just no excuse for how poorly relational databases handle hierarchical data.