multi-model Archives - Page 2 of 2 - ArangoDB

Sign up for ArangoGraph Insights Platform

Before signing up, please accept our terms & conditions and privacy policy.

What to expect after you signup
You can try out ArangoDB Cloud FREE for 14 days. No credit card required and you are not obligated to keep using ArangoDB Cloud.

At the end of your free trial, enter your credit card details to continue using ArangoDB Cloud.

If you decide that ArangoDB Cloud is not (yet) for you, you can simply leave and come back later.

Slides: Is multi-model the future of NoSQL?

00Future-of-nosql, PresentationTags: ,

Here is a slideshare and recording of my talk about multi-model databases, presented in Santa Clara earlier this month.

Abstract: Recently a new breed of “multi-model” databases has emerged. They are a document store, a graph database and a key/value store combined in one program. Therefore they are able to cover a lot of use cases which otherwise would need multiple different database systems. This approach promises a boost to the idea of “polyglot persistence“, which has become very popular in recent years although it creates some friction in the form of data conversion and synchronisation between different systems. This is, because with a multi-model database one can enjoy the benefits of polyglot persistence without the disadvantages.

In this talk I will explain the motivation behind the multi-model approach, discuss its advantages and limitations, and will then risk to make some predictions about the NoSQL database market in five years time. More info

7 reasons why ArangoDB is the world‘s best nosql database (or even better than that ;-))

00GeneralTags: ,
Note: We changed the name of the database in May 2012. AvocadoDB is now called ArangoDB.

Our mission: projects are different, project requirements change. We want to offer with AvocadoDB a most universally applicable nosql database which can be used in a maximum number of different use cases. In buzzword bingo language: we want to become the MySql in nosql – without MySql’s annoyances of course ;-).

More info