learnmeabitcoin.com - the bitcoin blockchain in Neo4j by Greg Walker
1 like2,576 views
The document discusses the use of Neo4j, a graph database, for managing and analyzing Bitcoin transactions. It outlines the experience and performance findings related to using Neo4j, including speed metrics and transaction sizes. Additionally, it emphasizes the advantages of using a graph database for handling the complex relationships inherent in blockchain data.
![My Experience
Tip
a
1
2
100
.
.
.
MERGE (a {id:’a’})
MERGE (n1 {id:1})
MERGE (n1)-[:r]→(a)
MERGE (n2 {id:2})
MERGE (n2)-[:r]→(a)
.
.
.
MERGE (n100 {id:100})
MERGE (n100)-[:r]->(a)](https://image.slidesharecdn.com/learnmeabitcoin-170401073247/85/learnmeabitcoin-com-the-bitcoin-blockchain-in-Neo4j-by-Greg-Walker-62-320.jpg)
![My Experience
Tip
a
1
2
100
.
.
.
MERGE (a {id:’a’})
FOREACH (x in [$list] |
MERGE (n:test {id: x.id})
MERGE (n)-[:test]->(a)
)
$list = {id:1}, {id:2} ... {id:100}](https://image.slidesharecdn.com/learnmeabitcoin-170401073247/85/learnmeabitcoin-com-the-bitcoin-blockchain-in-Neo4j-by-Greg-Walker-64-320.jpg)
learnmeabitcoin.com - the bitcoin blockchain in Neo4j by Greg Walker
- 2. About Me
- 3. About Me
- 4. About Me
- 5. About Me
- 6. About Me
- 7. About Me
- 8. About Me
- 9. About Me
- 10. About Me ...
- 11. About Me
- 12. About Me learn me a bitcoin
- 13. About Me learn me a bitcoin
- 14. About Me learn me a bitcoin
- 15. About Me learn me a bitcoin
- 16. Why I m using Neo4j’
- 17. Why I m using Neo4j’
- 18. Why I m using Neo4j’
- 19. Why I m using Neo4j’
- 20. Why I m using Neo4j’ ?
- 21. Why a graph database?
- 22. Why a graph database? Bitcoin Transactions:
- 23. Why a graph database? Bitcoin Transactions: 2
- 24. Why a graph database? Bitcoin Transactions: 2
- 25. Why a graph database? Bitcoin Transactions: 2 AddressGreg
- 26. Why a graph database? Bitcoin Transactions: 2
- 27. Why a graph database? Bitcoin Transactions: 2
- 28. Why a graph database? Bitcoin Transactions: 2 2
- 29. Why a graph database? Bitcoin Transactions: 2 2
- 30. Why a graph database? Bitcoin Transactions: 2 2 AddressMum
- 31. Why a graph database? Bitcoin Transactions: 2 2
- 32. Why a graph database? Bitcoin Transactions: 2 1.5 0.5
- 33. Why a graph database? Bitcoin Transactions: 1 0.8
- 34. Why a graph database? Bitcoin Transactions: 1
- 35. Why a graph database? Bitcoin Transactions:
- 36. Why a graph database? Bitcoin Transactions:
- 37. Schema
- 41. Schema (Advantages of a Graph Database)
- 42. Schema (Advantages of a Graph Database)
- 43. Schema (Advantages of a Graph Database)
- 44. Schema (Advantages of a Graph Database)
- 49. My Experience
- 51. My Experience Size 100 GB 500 GB
- 52. My Experience Size 100 GB 500 GB 1,325,071,942 nodes 2,020,670,961 relationships
- 55. My Experience Speed “Hot” = 0.2 secs “Cold” = 8.5 secs
- 56. My Experience Speed “Hot” = 0.2 secs “Cold” = 8.5 secs RAM
- 57. My Experience Speed “Hot” = 0.2 secs “Cold” = 8.5 secs RAM SSD
- 62. My Experience Tip a 1 2 100 . . . MERGE (a {id:’a’}) MERGE (n1 {id:1}) MERGE (n1)-[:r]→(a) MERGE (n2 {id:2}) MERGE (n2)-[:r]→(a) . . . MERGE (n100 {id:100}) MERGE (n100)-[:r]->(a)
- 63. My Experience Tip a 1 2 100 . . . MERGE (a {id:’a’}) $list = {id:1}, {id:2} ... {id:100}
- 64. My Experience Tip a 1 2 100 . . . MERGE (a {id:’a’}) FOREACH (x in [$list] | MERGE (n:test {id: x.id}) MERGE (n)-[:test]->(a) ) $list = {id:1}, {id:2} ... {id:100}