Meet Sheldon, Our Custom Database Server
From the post:
Building a recommendations engine is a challenging thing, but one thing that makes a difference is saving your data to make the whole process more efficient. Recommendation engines are fed by user interactions, so the first thought might be to use a graph processing system as a model that lets you abstract the whole system in a natural way. Since Moviepilot Labs is working with a graph database system to store and query all our data we built Sheldon, our custom graph database server.
I suppose being a movie recommendation service that it is only appropriate that it start with a teaser about its graph database server.
The post ends:
This article is Part 1 of a two-part series on graph databases being used at Moviepilot.Read about how Moviepilot walks the graph in Part 2. Learn more about graph databases here.
The pointer is a good source of information but still no detail on “Sheldon.”
[…] The prior post in this series was: Meet Sheldon, Our Custom Database Server. […]
Pingback by How Moviepilot Walks The Graph « Another Word For It — December 22, 2011 @ 7:41 pm