As the industry awakens to the abuse of relational data modeling, the graph datastore arises as a compelling choice for many data needs. This may not be extremely obvious to those who have been raised in the RDBMS era for use beyond social networking. Even if you aren’t working at Facebook or in a similar space (or even with jvm languages), there are many reasons you may want to look at a graph for your data needs, specifically Neo4j.

In this session I will discuss Neo4j and it’s uses. We’ll talk about what makes it different from aggregate data stores and then look at the query language, Cypher, and the server management tools that make it a real option for enterprises. Hopefully by the end of this session you will see graph data stores as one of the tools for your polyglot persistence needs.


Amanda Laucher is currently working with Neo Technology, the company behind Neo4j. She is a language geek who is often found ranting about functional languages and great type systems. You may know her as @pandamonial on twitter or from previous conference sessions on F#, FP, DSLs, Type systems, Agile methodologies, or any number of other topics that make her passionate about software development.