Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>So I've tested and been working with graph databases for the last year. I think only you know your data well enough to be able to make an educated guess as to whether you're going to have any nodes needing more than 32 billion relationships. I would argue there are not a lot of use cases right for most people where this is a limitation. But that's not absolute.</p> <p>Neo4j is a brilliant product. Well documented and with folks like maxdemarzi writing excellent blog posts - such as: <a href="http://maxdemarzi.com/">http://maxdemarzi.com/</a> - which will bring anyone up to speed on the power and sophistication of neo4j pretty quickly. (Plus he's a nice guy who'll answer your questions if you have them)</p> <p>If scale is an issue I'd also recommend you take a look at Titan - <a href="http://thinkaurelius.github.com/titan/">http://thinkaurelius.github.com/titan/</a>. The guys behind this are brilliant and it's intended for massive scale. It's not as established in the market as neo4j but it has a lot of power and gives you some flexibility on priorities by letting you select between Cassandra, Hbase and BerkeleyDB for underlying storage.</p> <p>Neo4j is a well backed, well funded company with real revenues. It isn't going anywhere. Titan is smaller but I think is on a rapid upward curve.</p> <p>The truth is though it's all a new space. You're not getting anything as established as Postgres, MySql or the corporate strength of Oracle. Let's not kid ourselves.</p> <p>However the graph database community is relatively small, friendly and helpful. It runs great events - I was at Neo4j's GraphCon event which was awesome, and I've been to some talks by the Titan guys which were great. Ultimately if you want to be Facebook though, whatever you start with you'll end up building your own infrastructure. There's scale and then there's you-need-to-own-datacenters-the-size-of-small-countries scale.</p> <p>One final thought. The problem of 40 million users and your underlying infrastructure challenges is a problem for a well established well funded company. You don't get to 40 million users and not attract the funding or generate the revenue necessary to finance building out your own infrastructure. You can plan now for when you're 40 million users, absolutely. Go for it. That's the fun of early stages in a startup. But your bigger problem is getting to your first million or ten million even. For that use whichever of these databases gets you to market fastest with a solid product.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload