Graph All The Things! - Andreas Kollegger @ Neo4j GraphDays: #AllYouCanGraph Palo Alto 2014
Recent years have seen an explosion of technologies for managing, processing and analyzing graphs. While the most well known users of graph technologies have been social web properties such as Facebook and LinkedIn, a quiet revolution has been steadily spreading across other industries. In this last 18 months, more than 30 of the Global 2000, and many times as many startups, have quietly been working to apply graphs to a wide array of business-critical use cases. For example: one of the world’s top parcel delivery carriers wasn’t going to be able to handle Christmas volumes last year because of numerous challenges stemming from online ordering. The solution? Replace the legacy routing system with a graph database, which now routes 5M packages per day in real time: faster and more efficiently than its relational cousins ever could. One of the top investment banks now onboards traders using an identity & access management system based on graphs. Media metadata turns out to be best represented as a graph; and consumers respond well to the opportunity to visually navigate the graph (such as is done by the app Discovr Music). Similar trends are developing in telecommunications, healthcare, human resources, gaming, and many more. We are entering an era of connected data: where those companies that can master the connections between their data – the lines and patterns linking the dots, and not just the dots – will outperform the companies that fail to recognize connectedness.
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Mehr von Neo4j
Mehr von Neo4j (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Graph All The Things! - Andreas Kollegger @ Neo4j GraphDays: #AllYouCanGraph Palo Alto 2014
- 1. Graph all the Things A story of data and relationships Andreas Kollegger Product Designer @akollegger
- 10. ALS Lou Gehrig's Disease Amyotrophic lateral sclerosis motor neurone disease Charcot disease MND ICD-10 G12.2 ICD-9 335.20 OMIM 105400 2005: Lusaka, Zambia
- 11. ALS Lou Gehrig's Disease Amyotrophic lateral sclerosis motor neurone disease Charcot disease MND ICD-10 G12.2 ICD-9 335.20 OMIM 105400 2005: Lusaka, Zambia ALS Lou Gehrig's Disease Amyotrophic lateral sclerosis motor neurone disease Charcot disease MND ICD-10 G12.2 ICD-9 335.20 OMIM 105400
- 12. ALS Lou Gehrig's Disease Amyotrophic lateral sclerosis motor neurone disease Charcot disease MND ICD-10 G12.2 ICD-9 335.20 OMIM 105400 2005: Lusaka, Zambia SNOMED? ALS Lou Gehrig's Disease Amyotrophic lateral sclerosis motor neurone disease Charcot disease MND ICD-10 G12.2 ICD-9 335.20 OMIM 105400
- 13. ALS Lou Gehrig's Disease Amyotrophic lateral sclerosis motor neurone disease Charcot disease MND ICD-10 G12.2 ICD-9 335.20 OMIM 105400 2005: Lusaka, Zambia SNOMED? LOINC? ALS Lou Gehrig's Disease Amyotrophic lateral sclerosis motor neurone disease Charcot disease MND ICD-10 G12.2 ICD-9 335.20 OMIM 105400
- 14. ALS Lou Gehrig's Disease Amyotrophic lateral sclerosis motor neurone disease Charcot disease MND ICD-10 G12.2 ICD-9 335.20 OMIM 105400 2005: Lusaka, Zambia SNOMED? LOINC? Non-English terms and local idioms? ALS Lou Gehrig's Disease Amyotrophic lateral sclerosis motor neurone disease Charcot disease MND ICD-10 G12.2 ICD-9 335.20 OMIM 105400
- 15. ALS Lou Gehrig's Disease Amyotrophic lateral sclerosis motor neurone disease Charcot disease MND ICD-10 G12.2 ICD-9 335.20 OMIM 105400 2005: Lusaka, Zambia SNOMED? LOINC? Non-English terms and local idioms? ALS Lou Gehrig's Disease Amyotrophic lateral sclerosis motor neurone disease Charcot disease MND ICD-10 G12.2 ICD-9 335.20 OMIM 105400 Categories and Indicators and Related Conditions and Treatments and Drugs?
- 16. Hey, who wants to come to Sweden to hack on Neo4j for 6 months?
- 17. 2000: Sweden
- 18. 2000: Sweden
- 19. 2000: Sweden
- 20. 2000: Sweden
- 21. 2000: Sweden
- 22. Graphs are not a new idea, just the right idea right now.
- 23. 1736: Königsberg
- 24. A B D C 1736: Königsberg 7 Bridges Problem
- 25. A B D C 1736: Königsberg 7 Bridges Problem
- 26. A B D C 1736: Königsberg 7 Bridges Problem
- 27. A B D C 1736: Königsberg 7 Bridges Problem
- 28. A B D C 1 2 3 4 7 6 5 1736: Königsberg 7 Bridges Problem
- 29. A B D C 1 2 3 4 7 6 5 1736: Königsberg 7 Bridges Problem
- 31. Neo Technology, Inc Confidential
- 35. NOSQL == Not Only SQL
- 36. Hint: Relationships Matter Put all of us into a database. ! Ask an RDBMS: “What's the average age of everyone here?” ! Ask Neo4j: “Who should I get to know better?”
- 37. Member Group
- 39. Member Group 143 Andreas 326 Stockholm 725 San Francisco 981 Boston
- 40. Member GroupMember_Group 143 Andreas 326 Stockholm 725 San Francisco 981 Boston
- 41. Member GroupMember_Group 143 Andreas 326 Stockholm 725 San Francisco 981 Boston 143 981 143 725 143 326
- 42. Andreas India San Francisco Boston 143 326 725 981 143 981 143 725 143 326
- 44. Property Graph
- 49. Nodes uid: ABK name: Andreas uid: STK where: Stockholm uid: SFO where: San Francisco uid: BOS where: Boston Member Group Group Group with Labels Relationships with Type MEMBER_OF MEMBER_OF MEMBER_OF since: 2009 since: 2013 since: 2012 Property Graph
- 50. Nodes uid: ABK name: Andreas uid: STK where: Stockholm uid: SFO where: San Francisco uid: BOS where: Boston Member Group Group Group with Labels Relationships with Type MEMBER_OF MEMBER_OF MEMBER_OF since: 2009 since: 2013 since: 2012 Properties on both Property Graph
- 51. What about the wolves?!? Tell me about the wolves!
- 52. How Wolves Change Rivers: Research Results
- 53. How Wolves Change Rivers: Known Influences Modeled as a Graph
- 54. How Wolves Change Rivers: Known Influences Modeled as a Graph
- 55. How Wolves Change Rivers: Query for Trophic Cascades ! MATCH path = (:Animal {Entity:"Wolves"})-[*]->(:Landscape {Entity:"Rivers"}) WITH extract(node IN nodes(path) | node.Yellowstone) AS factor, rand() AS number RETURN factor AS How_Wolves_Affect_RiverStability ORDER BY number LIMIT 5
- 56. How Wolves Change Rivers: Query for Trophic Cascades ! MATCH path = (:Animal {Entity:"Wolves"})-[*]->(:Landscape {Entity:"Rivers"}) WITH extract(node IN nodes(path) | node.Yellowstone) AS factor, rand() AS number RETURN factor AS How_Wolves_Affect_RiverStability ORDER BY number LIMIT 5
- 61. Thank you! Think about relationships, Follow paths, Find your graph