World’s Fastest most Scalable Graph Database

VelocityGraph is an open source C# .NET hybrid NoSQL Graph Database and Object Database that can be Embedded/Distributed.

Slide background




Faster Database

with the latest technologies and no dependencies

More Scalable Database

with encryption and LZ4 compression

More options

with a GUI Database Manager

Cross Platform

Windows 10 PC & Phone, Xbox,

Xamarin iOS, Android and Linux

Import & Export

to/from csv files and JSON

Orders of Magnitude
than SQL and other NoSQL
Image layer

Time (s) to discover 285730264 triangles by combining 86,220,856 tuples

Image layer
More compact data
than SQL and other NoSQL

Database Size (MB)

Image layer

Welcome to VelocityDB Video


Oliwia Persson

Using VelocityGraph saves time and money for all software requiring reliable, high performance data persistence. The use of VelocityGraph can be hidden from your application user's and doesn't require a team of database administrators (DBA's).

What is OODB?

An object database allows software developers to develop application data models, store them as objects, and replicate or modify existing objects to make new objects within the object database system. The database is integrated with the programming language, allowing the developer to maintain consistency within one environment, since both the database system and the programming language will use the same model of representation.

Among other benefits, this architecture eliminates the need for a cumbersome mapping layer between the database model and the application data model.

In order to be fully productive with an object oriented database, you need to purge your relational database thinking and think object oriented, a good book about this is "Object Thinking".

Object vs Relational

A relational database stores all data in tables on a server. Clients talk to such servers using SQL statements such as "select * from actors". Data is also created and updated using SQL. VelocityDB is not a relational database (but it is very good at managing relations!), with VelocityDB C# objects are stored as objects with all references/relations between the objects. Using VelocityDB persistent C# objects is very similar to using in memory C# objects. Data is created by creating C# objects; updates are accomplished by updating C# objects. The persistent store is safely done using transactions with locking protection so that one user can't accidently undo other user's changes. Like most database systems, VelocityDB uses paging but unlike other systems VelocityDB data pages have variable size and can optionally be encrypted and compressed. VelocityDB persistent objects have an object identifier (Oid) consisting a DatabaseNumber-PageNumber-SlotNumber.


The most important benefit is the flexibility that this database system provides. No other types of database system lets you fine tune your application to the finest details. Using VelocityDB, you can choose the best possible data structures for your application. You can control exactly where you place the data persistently. The placement choice can make a huge difference for performance. With VelocityDB you will have the ultimate tool for persisting data efficiently with unbeatable performance.

Unstructured Data can be managed efficiently using VelocityDB. Several of the sample applications provided with the download explore unstructured data. The triangle counter test demonstrates how efficient it is to follow association/relations. In memory, an association in VelocityDB is simply a C# object reference. It can't get any more efficient than that. The Kevin Bacon Numbers sample is another example showing how efficient we can handle unstructured data. A common way to manage unstructured data is to add such data to an inverted index. That way we can efficiently query such data, like if we want to know what store products that match one or more words. The entire Google search mechanism is based on an inverted index. In some of our samples we use inverted indexes, these samples include; TextIndexer and Wikipedia.

A shopping web site in prototype production uses an inverted index to help shoppers find products they are looking for, try the product search here (it is not always online).  It currently manages about 30 million products from about 650 stores (~33 GB of data).

VelocityDB is extremely scalable; it can handle small applications with small amounts of persistent data as well as applications using trillions of objects up to about an Yottabyte in size per session. Unlimited number of sessions can be used per application. Performance is fantastic, a billion Person object database is quickly created, a little over 1 hour, and can be browsed with the VelocityDbBrowser.

Why use a Database?

It depends on the situation. Maybe your application data is getting too large to hold in memory? By using a database you can limit the memory usage of your application without sacrificing performance.

You may have written your own flat file storage instead of using a database. This may have worked fine but now your application requirements are changing. There is more data and maybe multiple users who want access to the data at the same time. Conventional databases, SQL based relational databases, may not be what you need but a powerful, yet easy to use, object database can replace your in house built data storage solution. VelocityDB is fully transactional, supporting ACID properties, your application can make a GB or more of changes and it can all be undone with a simple transaction abort or if your application suddenly crashes, incomplete changes made to your data will automatically be undone by the recovery mechanism. Multiple users have access to the data from anywhere and can all make changes to the data without accidentally overwriting somebody else’s changes.

Why not SQL (NoSQL) ?

Relational databases and Standard Query Language (SQL) was invented in the 70ties, almost half a Century ago. It was good for its time but computer capabilities are about a million times improved and these days object oriented languages rule.

It's time for a replacement/complement to SQL and relational databases. We believe that object oriented and graph databases are ideal for today's complex applications using Object Oriented languages like C#, C++, Objective-C, Java, Python and Smalltalk.

If we are given a chance to prove it, we have the technology that can outperform traditional SQL solutions both in cost and performance.

System Requirements

To use VelocityDB you need to have Visual Studio 2010/2012/2013/2015 C# (using .NET 4.5 or above and a Windows 10 PC (other Windows versions OK if recent). Other .NET languages may also be used. SharpDevelop is a free light weight alternative to Visual Studio. Some versions of Visual Studio are also free.  MacOS and Linux platforms are available by using the cross platform, open source .NET development framework mono or Xamarin.

Usage Choices

Use VelocityDB standalone on a single PC or use unlimited distributed clients with unlimited distributed servers.

Standlone version can do almost everything that the client + server(s) version can do. See the feature table comparison for the differences.

Not using .NET?, deploy to C++/Java or whatever language you want

First define your data model using .NET then we can provide a deployment tool to other object oriented languages such as C++ or Java. Even deploy to multiple languages for concurrent usage. We can build this feature on request for a fee.

REST interface to VelocityDB databases

We recently started work on a REST interface to VelocityDB. This will enable database access from any web application, REST is implemented as a web api where you can use any http browser to access and update VelocityDB databases. We offer consulting services at a reasonable cost. Contact, if you are interested. We can help you develop your VelocityDB/VelocityGraph applications. Hadoop is popular right now so we might adapt VelocityDB to become a HDFS replacement like Cassandra is. We can build these features or any other on request for a fee.

Google Ads