Azsure DB Vs Graph Desktop Memory for Social Networking Application

I'm starting to work on some architecture for a .Net social networking application that will be hosted on the Azure cloud. we will use ASP.NET MVC on the front panel.

I would like to consider storage options. Given the need for scalability and the interconnected nature of the application, SQL azure is excluded.

what are the main considerations when choosing a graphical DB, such as Sones GraphDB or neo4j, which have features specific to a social networking application, versus using azure table storage to store data to meet your needs.

I am mostly concerned about development time, cost, the ability to use existing skills such as .NET, and the reliability of graphical DB platforms, as well as the ease of setup and administration.

+3
source share
1 answer

Graphic databases are designed for applications such as social networks. For ease of development, it is best to start with something like GraphDB. A key advantage over a key database is its powerful query and crawl capabilities. For example, it would be easy to find all occurrences of friends of friends using the GraphDB query syntax.

, Azure Table, - , . 500 Azure . , Visual Studio SDK . - , , , , / . Azure Table . https://azure.microsoft.com/en-us/documentation/articles/storage-table-design-guide/

0

Source: https://habr.com/ru/post/1794128/


All Articles