nosql - Graph DB's Vs Azure Table storage for a Social networking application -


i'm starting on architecture work .net based social networking application hosted on azure cloud. going using asp.net mvc on front end.

i consider options storage. considering scalability needs , due inter-connected nature of application, sql azure has been ruled out.

what main considerations in choosing graph db such sones graphdb or neo4j have features specific social networking application against using windows azure table storage achieve needs.

i'm concerned development time, cost, ability leverage existing skills .net , reliability of graph db platforms , ease of setup , administration.

graph databases designed applications such social networks. ease of development, may best start graphdb. key advantage on key-value database powerful query , traversal capabilities. easy to, instance, find occurrences of friends of friends using graphdb query syntax.

the benefit of key-value database service azure table low cost, minimal administrative overhead , scalability. can store 500tb of data per azure storage account , setup accounts in multiple regions. there no server setup or database administration overhead , visual studio sdk easy use. down side graph query support not built in , must index off primary key / row key pair. additional azure table design pattern please see https://azure.microsoft.com/en-us/documentation/articles/storage-table-design-guide/


Comments

Popular posts from this blog

linux - Mailx and Gmail nss config dir -

c# - Is it possible to remove an existing registration from Autofac container builder? -

php - Mysql PK and FK char(36) vs int(10) -