megree chooses Neo4j for its scalability, REST API and high availability

The Challenge

Kevin Dieter, co-founder and CTO, chose Neo4j when preparing to launch the social solution megree. The decision became clear when observing Neo4j’s REST API and scaling capabilities.

When Dieter joined megree, it was a .NET based project in alpha testing stages, running on a Microsoft SQL Server. Upon looking at scaling potential and the heavy logic issues, it was apparent that a SQL solution would not suffice.

Neo4j was chosen for its REST API, graph traversal performance, and high availability. Another key element was Neo4j’s proven scalability to a high number of nodes/ relationships in a graph.

The Solution

With only two months of implementation time, megree met their primary business objectives, and met their scaling and REST API necessities.

Neo4j was originally only to be used to demonstrate relationships between users, however with its ability to quickly traverse the data, megree now looks to expand Neo4j to more aspects of the technology

Download Case Study