用于社交网络应用程序的图形数据库与 Azure 表存储
我正在开始为托管在 Azure 云上的基于 .Net 的社交网络应用程序进行一些架构工作。我们将在前端使用 ASP.NET MVC。
我想考虑存储选项。考虑到可扩展性需求以及应用程序的互连性质，SQL azure 已被排除。
选择具有特定于社交网络应用程序功能的图形数据库（例如 Sones GraphDB 或 Neo4j）时的主要考虑因素是什么，而不是使用 Windows Azure 表存储来满足需求。
我最关心的是开发时间、成本、利用 .NET 等现有技能的能力、图形数据库平台的可靠性以及设置和管理的简易性。
I'm starting on some architecture work for a .Net based social networking application to be hosted on Azure cloud. we are going to be using ASP.NET MVC on the front end.
i would like to consider the options for storage. considering scalability needs and due to the inter-connected nature of the application, SQL azure has been ruled out.
what would be the main considerations in choosing a graph DB such as Sones GraphDB or neo4j which have features specific for a social networking application against using windows azure table storage to achieve the needs.
i'm mostly concerned about development time, cost, ability to leverage existing skills like .NET and reliability of the graph DB platforms and ease of setup and administration.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
图数据库是为社交网络等应用程序设计的。为了便于开发，最好从 GraphDB 之类的东西开始。相对于键值数据库的一个关键优势是强大的查询和遍历功能。例如，使用 GraphDB 查询语法可以很容易地找到所有出现的朋友的朋友。
Azure Table 等键值数据库服务的优点是成本低、管理开销最小，并且具有可扩展性。每个 Azure 存储帐户和多个区域中的设置帐户可以存储 500TB 的数据。没有服务器设置或数据库管理开销，并且 Visual Studio SDK 易于使用。缺点是没有内置图形查询支持，您必须从主键/行键对建立索引。有关其他 Azure 表设计模式，请参阅 https:// azure.microsoft.com/en-us/documentation/articles/storage-table-design-guide/
Graph databases are designed for applications such as social networks. For ease of development, it may be best to start with something like GraphDB. A key advantage over a key-value database is powerful query and traversal capabilities. It would be easy to, for instance, find all occurrences of friends of friends using the GraphDB query syntax.
The benefit of a key-value database service like Azure Table is low cost, minimal administrative overhead and scalability. You can store 500TB of data per Azure storage account and setup accounts in multiple regions. There is no server setup or database administration overhead and the Visual Studio SDK is easy to use. The down side is that graph like query support is not built in and you must index off the Primary Key / Row Key pair. For additional Azure Table design pattern please see https://azure.microsoft.com/en-us/documentation/articles/storage-table-design-guide/