Presented by, Vinita Talreja 13MCEC28 MTech. CSE

BASIC ARCHITECTURE IG Core/API Objectivity/DB Distributed Database User Apps Blueprints IG Core/API Management Extensions Navigation Execution Placement Session / TX Management Configuration Objectivity/DB Distributed Database

TECHNICAL SPECIFICATIONS Written in: Java (core C++) Platforms: Windows (32-bit and 64-bit), Linux (32-bit and 64-bit), Mac (64-bit) API/Protocols: Java, Tinkerpop (which provides Gremlin, REST, Frames, Ripple and Linked Process) Consistency: Flexible (from ACID, to relaxed) Indexing: Flexible (from automatic to manual) Persistence: Java class based.

Creating a Database GraphFactory.create(dbname) GraphFactory.create(dbname,propertiesfile) Fig: Files created on creation of database Ref: https://wiki.infinitegraph.com

Boot file The boot file (mySystemName.boot) includes all the information needed to open a graph database. When an application interacts with a graph database, it establishes the connection through the boot file. The boot file lists the location of the graph's system database file (mySystemName.fdb), which is a binary file that stores information about your graph.

Using the database GraphFactory.open(dbname) GraphFactory.open(dbname,propertiesfile)

Adding data The first time persistent elements are added to the graph, DATABASE files are created to store those elements, and the locations of those database files are added to the system database file. The schema definitions for the elements are also added to the system database file. Each new persistent element is given a unique identifier and stored in the appropriate database file (handled by InfiniteGraph's managed placement system). As applications make updates to the graph, JOURNAL files are created. These files are used to return the graph to its previously committed state if a transaction is aborted or terminated abnormally.

Ref: http://wiki.infinitegraph.com/ Fig: Files Ref: http://wiki.infinitegraph.com/

System Files Vertex instances are placed in VertexGroup_n.systemName.DB Edge instances are placed in EdgeGroup_n.systemName.DB Internal information related to edges is stored in ConnectorGroup_n.systemName.DB.

Add vertices and edges Meets Calls Pays Vertex vinita= myGraph.addVertex(new Person(“Vinita”)); Vertex shalini = myGraph.addVertex(new Person(“Shalini”)); Vertex shraddha= myGraph.addVertex(new Person(“Shraddha”)); Vertex rajvi= myGraph.addVertex(new Person(“Rajvi”)); vinita.addEdge(new Meeting(“Denver”, “5-27-10”), shalini); shalini.addEdge(new Call(timestamp), shraddha); shraddha.addEdge(new Payment(100000.00), rajvi); shalini.addEdge(new Call(timestamp), rajvi); Vinita Rajvi Shalini Meets Calls Pays Shraddha

Ref: https://wiki.infinitegraph.com LOCAL DATA ACCESS Fig: Local Data Access Ref: https://wiki.infinitegraph.com

DISTRIBUTED DATA ACCESS

REFERENCES https://wiki.infinitegraph.com Whitepaper: InfiniteGraph: The Distributed Graph database

THANK YOU!