GraphDB-Lite Introduction

Skip to end of metadata
Go to start of metadata
Search
This documentation is NOT for the latest version of GraphDB.

Latest version - GraphDB 7.1

GraphDB Documentation

Next versions

GraphDB 6.3
GraphDB 6.4
GraphDB 6.5
GraphDB 6.6
GraphDB 7.0
GraphDB 7.1

Previous versions

GraphDB 6.0 & 6.1

OWLIM 5.4
OWLIM 5.3
OWLIM 5.2
OWLIM 5.1
OWLIM 5.0
OWLIM 4.4
OWLIM 4.3
OWLIM 4.2
OWLIM 4.1
OWLIM 4.0

This chapter briefly explains the purpose and the scope of this document, its place in the GraphDB user documentation set, and provides some suggestions for efficient use. It starts with an introduction on the differences between the two editions of GraphDB, which facilitates the understanding of the GraphDB product family, the design objectives behind each of the versions, and the rationale behind the structuring of the documentation.

GraphDB Editions

GraphDB-Lite and GraphDB-SE are identical in terms of usage and integration. Apart from a few differences in configuration parameters, these editions have the same functionality and implement the same Sesame APIs. However, they use different indexing, inference and query evaluation implementations, which result in different performance, memory requirements, and scalability.

GraphDB-Lite is designed for medium data volumes (below 100 million statements) and for prototyping. Its key characteristics are as follows:

  • reasoning and query evaluation are performed in main memory;
  • it employs a persistence strategy that ensures data preservation and consistency;
  • the loading of data, including reasoning, is extremely fast;
  • easy configuration.

GraphDB-SE is suitable for handling massive volumes of data and very intensive querying activities. It is designed as an enterprise-grade database management system. This has been made possible through:

  • file-based indices, which enable it to scale to billions of statements even on desktop machines;
  • special-purpose index and query optimisation techniques, ensuring fast query evaluation against very large volumes of data;
  • optimised handling of owl:sameAs (identifier equality) to boost efficiency for data integration tasks;
  • efficient retraction of explicit statements and their inferences, which allows for efficient delete operations.

GraphDB-Enterprise is a component that can manage and synchronise multiple GraphDB instances in a resilient and scalable cluster configuration.

Further discussion on the differences between GraphDB's editions can be found in the GraphDB Primer.

Purpose, Intended Readership and Overview of this Document

This document is designed for software engineers, system integrators and system administrators who wish to integrate the GraphDB-Lite semantic repository in to their applications or who wish to use GraphDB-Lite and Sesame as a stand-alone server for storing and processing structured data. It is also useful for system administrators who need to support and maintain a GraphDB-Lite repository.

The reader is assumed to be familiar with databases, but not an expert in semantic database systems, semantic information retrieval, Semantic Web, or GraphDB itself. Less experienced readers are recommended to read the GraphDB Primer where the required minimum of Semantic Web and related concepts is covered, as well as GraphDB basics.
This document has multiple uses:

  • To provide the information necessary to use GraphDB-Lite repositories via the Sesame APIs;
  • To give instructions on managing repositories through the Sesame web front-end;
  • For familiarisation with GraphDB-Lite reasoning capabilities and rule language;
  • To enable the creation of custom installations and configurations of GraphDB-Lite;
  • To introduce the most important factors that affect the efficiency of GraphDB-Lite and to provide some productivity tips.

How to Use This Document

Readers new to GraphDB should read the GraphDB Primer first and then this document in its entirety. This will guarantee that the necessary basic information has been covered in sufficient depth. After some experience using GraphDB, this guide can be used as a reference for carrying out specific tasks.
The following conventions are used in this document:

  • Code examples are listed in a typewriter-like font;
  • Other important terms, when first introduced, are written in italics;
  • Formulas are always in italics;
  • References are given in square brackets, e.g. [3] means "Refer to publication #3 in the References section";
  • GraphDB-Lite, GraphDB-SE and GraphDB-Enterprise are referred to collectively as "GraphDB" in those cases where it is not necessary to distinguish between the editions, i.e. the specifications, features, and/or settings described are common for all editions.
Labels:
None
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.