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

问题描述

我需要设计/架构/开发一个基于网络的社交网络类型的应用程序.

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.

从 SQL 的角度(任何数据库)来看，这会是什么样子?
从 NOSQL 的角度(任何 NOSQL 数据库)来看，这会是什么样子?

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?

谢谢

推荐答案

像 http://www.neo4j 这样的图形数据库.org 是一个值得考虑的选择.它非常适合社交网络(例如 http://blog.neo4j.org/2009/09/social-networks-in-database-using-graph.html)和基于 ACL 的安全性(例如 http://wiki.neo4j.org/content/ACL).

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屋！