ISWC Meetup with Neo4J: Difference between revisions

From lotico
Jump to navigation Jump to search
No edit summary
No edit summary
Line 8: Line 8:
Video
Video
  Ra'Shaun Stovall
  Ra'Shaun Stovall
Speaker
Emil Eifrem


Location
Location

Revision as of 09:27, 5 March 2019

Video

Lotico Meetup with Neo4J at ISWC 2009

Date

October 27, 2009

Video

Ra'Shaun Stovall

Speaker

Emil Eifrem

Location

ISWC 2009

Site:

http://neo4j.org

Neo4j - The Benefits of Graph Databases

Emil Eifrém, CEO Neo4j

Description

Meet Emil Eifrém CEO Neo Technology, founder of the Neo4j graph database project and CEO of Neo Technology. Programmer by passion the first 15 years on this planet and by passion & profession the remaining 15. First free software project at age 16. Now mainly focused on spreading the word about the powers of graphs and preaching the demise of tabular solutions everywhere. Presents regularly at conferences such as JAOO, Oredev, QCon, and OSCON.

Many applications today handle data that is deeply associative, i.e. structured as graphs (networks). The most obvious example of this is social networking sites, but even tagging systems, content management systems and wikis deal with inherently hierarchical or graph-shaped data.

This turns out to be a problem because it’s difficult to deal with recursive data structures in both traditional relational databases and many NoSQL stores. For example, in an RDBMS each traversal along a link in a graph is a join, and joins are known to be very expensive.

A graph database uses nodes, relationships between nodes and key-value properties instead of tables to represent information. This model is typically substantially faster for associative data sets and uses a schema-less, bottoms-up model that is ideal for capturing ad-hoc and rapidly changing data.

This session will introduce an open source, high-performance, transactional and disk-based graph database called “Neo4j” (http://neo4j.org), which frequently outperforms relational backends with >1000x for many increasingly important use cases.