New article: Graphs in the database, SQL meets social networks
Abstract: Graphs in the database: how to store a graph data structure in a DBMS, and answer the most common queries typical of social networks, like "You might also know" or "You might also like", or "How you are connected to XYZ" (degrees of separation).
This morning a new article of yours truly has been published on the TechPortal.
The title is Graph in the database: SQL meets social networks, and it's a natural sequel to my talk about Trees in the database.
You will learn how to retrieve linked nodes, and how to answer some of the queries typical of social networks like LinkedIn, Facebook, or recommendation systems ("You might also know/like", "How you are connected to XY", ...).
A special "thank you" to my colleague and friend Ian for reviewing the article with patience and a lot of suggestions.
» Have a nice reading!
- On batching vs. latency, and jobqueue models
- Updated Kafka PHP client library
- Musings on some technical papers I read this weekend: Google Dremel, NoSQL comparison, Gossip Protocols
- Historical Twitter access - A journey into optimising Hadoop jobs
- Kafka proposed as Apache incubator project
- NoSQL Databases: What, When and Why (PHPUK2011)
- PHPNW10 slides and new job!
4 responses to "New article: Graphs in the database, SQL meets social networks"
Rebecca, 17 January 2011 09:03
Hi. I've read your post on TechPortal and it's really great. I'm a programmer and SQL and Database are familiar with me. Reading your post is an additional info for me. :-)
Jason Sholts, 30 January 2011 13:29
Does anyone knows if one of implementations for this for let's say social networks was behind the FaceBook App - "Face" When each profile can be connected to another profile with "6 degrees of inner separation"
клиники германии, 21 April 2011 10:52
Trees in the database in social networks and SQL are so up to date! I have read it and it was very interesting.
Bryan P. Cruz, 21 June 2011 22:46
These are great tips for social networking, aseptically I liked your approach which was generic and efficient.