Download to read offline
Uploaded byOliver Busse
GraphDb in XPages
This document discusses implementing graph database capabilities in XPages. It begins with introductions of the presenter Oliver Busse and an overview of graph databases. It then discusses some graph database products and frameworks as well as companies using graph databases. Key terminology for graphs like vertices, properties, and edges is defined. The document explains how graphs could be implemented in Domino using documents to store vertices and edges and outlines the data modeling and initialization process. Code examples and a demo application are referenced for further information.
More Related Content
![Lect 1 Number systems and base conversions. [Autosaved].pptx](https://cdn.slidesharecdn.com/ss_thumbnails/lect1numbersystemsandbaseconversions-260111134109-67c2d865-thumbnail.jpg?width=640&height=640&fit=bounds)
GraphDb in XPages
- 1. Where is mydata? Implementing GraphDB capabilities in XPages Oliver Busse We4IT GmbH, Germany April 13, 2016
- 2. Oliver Busse • „BleedingYellow“ since R4.5 • Software Architect at We4IT • Member of the development team of Aveedo® Application Framework • IBM Champion for ICS in 2015 + 2016 • OpenNTF Member Director • XPages Advocate • IBM Bluemix curious @zeromancer1972 www.oliverbusse.com
- 3.
- 4. Graph DB A graphdatabase, also called a graph-oriented database, is a type of NoSQL database that uses graph theory to store, map and query relationships. A graph database is essentially a collection of nodes and edges. Each node represents an entity (such as a person or business) and each edge represents a connection or relationship between two nodes. http://whatis.techtarget.com/definition/graph-database
- 5. Some Graph DBs& Frameworks • Neo4J • OrientDB • DEX • Tinkerpop • Apache Lucene / Solr
- 6. Who is usingGraph DBs? • Amazon • Google • Facebook • …almost every application that offers something like • „related posts“ (blogs) • „others also bought this“ (shops) • collect relations and „likes“ • …
- 7. Graphs – terminology •Vertices (Nodes) • Properties (Key-Value pairs) • Edges • Connections, Relations between Vertices • ElementStores • for us: NSF databases • MetaverseIDs • Replica + UNID (hashed) • internal use only (don‘t care about them)
- 8. Graph DB –in Domino? • Vertices and Edges are stored as Documents • The data container is a NSF • The ElementStore defines the filepath to the NSF • An ElementStore can hold different types of Vertices • Usually you create one ElementStore for each Vertice type
- 9. Data Modelling &Implementation • Nodes are defined as Interfaces • Fields are defined as properties with Getter and Setter • Methods define how the Node can build Edges to other Vertices • Methods also return all Edges to a certain Vertice
- 10. Init the Graph •Define the Element Store(s) • Add Element Store(s) to the Graph Configuration • Define the DFramedTransactionalGraph object with the Graph Configuration • Work with the Graph object
- 11. Create an Edge •Parameterize Object 1 • Get Object 2 by a unique key • Call one of the „add“ methods of your Node class • Commit your changes
- 12. Let‘s see thedemo & some code
- 13. Resources • The XPagesdemo application • https://bitbucket.org/zeromancer1972/sutol-2015-oda-graph-demo • http://notesx.net:8090/obusse/ec16 • A nice glossary • http://www.intec.co.uk/from-xpages-to-web-app-glossary/ • OpenNTF Domino API • http://www.openntf.org/main.nsf/project.xsp?r=project/OpenNTF%20Domino%20API • http://www.openntf.org/main.nsf/project.xsp?r=project/OpenNTF%20Domino%20API%20Demo%20Database • Xots • http://www.intec.co.uk/xots-background-and-multithreaded-tasks-the-openntf-domino-api-way-part-one/ • http://www.intec.co.uk/xots-background-and-multithreaded-tasks-the-openntf-domino-api-way-part-two/ • http://www.intec.co.uk/xots-background-and-multithreaded-tasks-the-openntf-domino-api-way-part-three/ • Graphs • http://de.slideshare.net/ktree19/the-graph-revolution
- 14.