构建社交网络类型应用程序的模式？ [英] Patterns for building social network type applications?

问题描述

我需要设计/设计/开发基于网络的社交网络类型应用程序。

基本功能：

- 用户在系统

- 用户彼此同意朋友

- 用户在系统内创建内容

- 用户指定哪些朋友可以查看/编辑他们创建的内容

这个核心功能确实已经创建了很多次吗？对于如何实现这种事情，有没有最佳实践模式？

我最感兴趣的是这个数据库的外观。

从SQL透视图（任何数据库），这样会是什么样的？

从NOSQL的角度（任何NOSQL数据库），这样会是什么样的？ >

我最感兴趣的事情是，数据库中内容可见性的问题是如何解决的？即数据库/应用程序如何确保只有经过批准的朋友可能会看到用户创建的内容？

谢谢

解决方案

像 http://www.neo4j.org 的图形数据库是一个选择看看。它很好地适用于社交网络（例如 http://blog.neo4j.org/2009/09/social-networks-in-database-using-graph.html ）和基于ACL的安全性（例如 http://wiki.neo4j.org/content/ACL ）。

I need to design / architect / develop a web based social network type application.

Basic functionality:
- users create accounts on the system
- users agree to "friend" each other
- users create content within system
- users specifies which friends may view/edit content that they created

Surely this core functionality has been created many times before? Are there any best practice patterns out there for how to implement this sort of thing?

I'm most interested in how the database for this would look.

What would this look like from a SQL perspective (any database)?
What would this look like from a NOSQL perspective (any NOSQL database)?

The thing I am most interested in, is how is the question of "content visibility" solved within the database? i.e. how does the database/application ensure that only approved friends may see the user created content?

Thanks

解决方案

a Graph Database like http://www.neo4j.org is a choice to look at. It lends itself very well to both the social network (e.g. http://blog.neo4j.org/2009/09/social-networks-in-database-using-graph.html) and the ACL-based security (e.g. http://wiki.neo4j.org/content/ACL ).

这篇关于构建社交网络类型应用程序的模式？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！