I've no experience using the .Net libraries, but you could certainly use the REST interface which is getting a lot of love and attention from the development team and has a friendly web interface.
I think REST would be a great way to start, and then you can better evaluate the .Net libraries and see which one tackles any frustrations you have dealing through the REST interface. Digg built its own graph database in-house because at the time there were no suitable alternatives: http://about.digg.com/blog/how-digg-works LinkedIn is also built around a graph database, held in-memory (at least in mid-2008): http://hurvitz.org/blog/2008/06/linkedin-architecture The world of graph databases has changed significantly even in the past twelve months. 2011 is the first year that I would whole-heartedly recommend Neo4j. I don't know how one could consider building a social application without a graph database in 2011. If speed is a concern, you can always add Memcached as an in-memory key value store to cache results. Stephen 2011/2/20 Fatih ÖZKAN <[email protected]> > Hi Stephen > I am seriously considering to build my application on graph database but i > read about facebook, digg and linkedin use Key/value database. Why dont > they > use graph database? What is the differences between Key/Value and graph > databases. > And i am using .Net Framework 4.0 for my application. There is not too much > thing about .Net, tutorial,samples etc. There are some library for .net > ,Neo4RestNet,Neo4jRestSharp. Which one should i use and can i develop > strong > application with this library? > Fatih > -----Özgün İleti----- From: Stephen Cremin Sent: Sunday, February 20, > 2011 > 11:17 AM To: Neo4j user discussions Subject: Re: [Neo4j] Social Networks > And Graph Databases > Hi Fatih > Yes, a graph database can be a complete replacement, holding your user's > login data, profiles, pictures, etc. If you're using JRuby, there's a gem > that interacts with the excellent devise authentication system. > For photos and certain other media, it probably makes more sense to store > them on a Content Delivery Network (CDN) with references to them (and their > metadata) only in your graph database. > You can certainly mix and match databases and I think that's the future of > web applications. But if you're starting from scratch I'd suggest putting > everything into the graph database. > For pictures, I'd consider Amazon's S3 from the get go, and you can later > migrate to CloudFront if necessary. > Would love to hear alternate views. > Stephen > 2011/2/20 Fatih ÖZKAN <[email protected]> > > Hi, > > I am new to graph databases. I and my friends decided to make simple > > social > > network and i am researching about graph databases and other nosql > > databases. I like the idea of graph db and i want to use them but i have > > questions. My question is if i decided to use graph database am i need > > another database system like mysql or ms sql, There are a lot of social > > networks which are using graph,other nosql databases and relational > > databases together. Can i hold all my data in graph database. For example > > my > > users login data, such as email, password, user roles,pictures etc. > > > > Sincerely > > _______________________________________________ > > Neo4j mailing list > > [email protected] > > https://lists.neo4j.org/mailman/listinfo/user > > > _______________________________________________ > Neo4j mailing list > [email protected] > https://lists.neo4j.org/mailman/listinfo/user > > _______________________________________________ > Neo4j mailing list > [email protected] > https://lists.neo4j.org/mailman/listinfo/user > _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
