NoSQL claim was to use the right database model for the right domain. Bad news, in most cases a single database model is not enough! In last years NoSQL experienced a huge upward trend, offering new data models (Document, Graph, Key-Value…) to solve problems where old relational databases failed. Now people who have chosen NoSQL as an architecture component, realize that a single data model (even when richer that relational), is not enough for average needs.
This presentation discusses the latest technology innovations and the market’s demand for databases that combine more than one NoSQL model (ex. GraphDB, DocumentDB, Key/Value, Objects), like OrientDB. We discusses why graph databases are at the heart of the multi-model revolution and why we are approaching the end of NoSQL fragmented ecosystem where customers are forced to use multiple tools in their architectures. Benefits and compromises of this approach along with real world use cases will also be shared.