This document summarizes a presentation about keeping user generated content flexible using Neo4j. It introduces the speaker and his background in programming. It then discusses some caveats and outlines the agenda which includes problems, motivation and goals, the tech stack including Mustache and Spring Data Neo4j, why Neo4j was chosen, examples of a form builder and social forum, and a demo with some code. The presentation aims to show how Neo4j can be used to build a flexible UI for creating structured content and generating markup from that structure.

1. Innovate. Share. Connect.
Chicago June 12-13
Keeping User Generated ContentKeeping User Generated Content
Flexible with Neo4jFlexible with Neo4j
Greg JordanGreg Jordan

2. My background
• Manager of Web Development at Methodist Le Bonheur
Healthcare
• Ph.D. candidate focusing on qualitative usability
• 15 years of programming experience
• Java
• Content management systems
• Mobile development (iOS, Android and, yes, Blackberry)
• Working with Neo4j for about a year

3. Caveats
• Not just about Neo4j
• Three weeks ago
• Work in progress

4. Agenda
• Problems
• Motivation & Goals
• Tech stack
• Why Neo4j
• Examples
• Bit of code

6. Problems
• Projects
• Form Builder
• Social Forum

7. Motivation & Goals
• Project Motivation
• It’s the right tool
• Growth of graph DB usage
• Goals
• Build UI to create flexible structure
• Generate input markup from structure
• Generate input rules from structure
• Generate list & item display markup
• Speed kills

8. Now what?

12. Tech stack

13. Mustache
• "logic-less": no explicit control flow statements
• all control driven by data
• strong "separating logic from presentation”
• it is impossible to embed application logic in the Mustache templates*
* Depends on how you define logic

14. Mustache.java
Sam Pullara
@sampullara
• Works well with progressive
enhancement
• Mock data is replaced at runtime
• Used at twitter & netflix

15. Spring Data Neo4j
• Object-Graph-Mapping of annotated POJO entities
• Neo4jTemplate with convenient API, exception translation and optional
transaction management
• Cross-store support for partial JPA - Graph Entities

16. Using Spring Data Neo4j
Michael Hunger
@mesirii

17. Why Neo4j?
• A native java API
• Access via a RESTful server protocol
• There are lots of language bindings
• Proven with customers like Cisco, Adobe and Jive

18. Why Neo4j?
• Whiteboard friendly
• Relationships have 1st class status

19. Why Neo4j?
• Schema-less
• Semi-structured data
• Speed at getting connected data

20. Examples – Form Builder

21. Examples – Social Forum

22. Demo & Bit of Code
• Mustache
• Spring Data Neo4j
• Java reflection

23. Questions?
Greg Jordan
@gmjordan