Likelihood to Recommend If you want a serverless NoSQL database, no matter it is for personal use, or for company use, Google Cloud Datastore should be on top of your list, especially if you are using Google Cloud as your primary cloud platform. It integrates with all services in the Google Cloud platform.
Read full review Titan is definitely a good choice, but it has its learning curve. The documentation may lack in places, and you might have to muster answers from different sources and technologies. But at its core, it does the job of storing and querying graph databases really well. Remember that titan itself is not the whole component, but utilizes other technologies like cassandra, gremlin, tinkerpop, etc to do many other things, and each of them has a learning curve. I would recommend titan for a team, but not for a single person. For single developer, go with
Neo4j .
Read full review Pros Automatically handles shards and replication. Schema-less & NoSQL. Fully managed. Read full review Titan is really good for abstraction of underlying infrastructure. You can choose between different storage engine of your choice. Open source, backed by community, and free. Supports tinkerpop stack which is backed by apache. Uses gremlin for query language making the whole query structure standardized and open for extension if another graph database comes along in future. Read full review Cons It is hosted on GCP, which makes it harder if your company have multi-cloud strategy. When you want to migrate to other cloud providers, there can be a caveat. Read full review The community is lacking deep documentation. I had to spend many nights trying to figure many things on my own. As graph databases will grow popular, I am sure this will be improved. Not enough community support. Even in SO you might not find many questions. Though there are some users in SO who quickly answer graph database questions. Need more support. Would love an official docker image. Read full review Likelihood to Renew For the amount of use we're getting from Google Cloud Datastore, switching to any other platform would have more cost with little gain. Not having to manage and maintain Google Cloud Datastore for over 4 years has allowed our teams to work on other things. The price is so low that almost any other option for our needs would be far more expensive in time and money.
Read full review Alternatives Considered We selected Google Cloud Datastore as one of our candidates for our NoSQL data is because it is provided by Google Cloud, which fits our needs. Most of our infrastructure is on Google Cloud, so when we think about the NoSQL database, the first thing we thought about is Google Cloud Datastore. And it proves itself.
Read full review To be honest, titan is not as popular as
Neo4j , though they do the same thing. In my personal opinion, titan has lot of potential, but
Neo4j is easier to use. If the organization is big enough, it might choose titan because of its open source nature, and high scalability, but
Neo4j comes with a lot of enterprise and community support, better query, better documentation, better instructions, and is also backed by leading tech companies. But titan is very strong when you consider standards. Titan follows gremlin and tinkerpop, both of which will be huge in future as more graph database vendors join the market. If things go really well, maybe
Neo4j might have to support gremlin as well.
Read full review Return on Investment Simple billing part of Google Cloud Platform No time spent configuring and maintaining Google Cloud Datastore. Very good uptime for our applications. Read full review Steep learning curve. Your engineers would have to spend lots of time learning different components before they feel comfortable. Have to plan ahead. Maybe this is the nature of graph databases, but I found it difficult to change my schemas after I had data in production. It is free, so time is the only resource you have to put in titan. Read full review ScreenShots