What is Titan and what are its top alternatives?
Top Alternatives to Titan
Neo4jNeo4j stores data in nodes connected by directed, typed relationships with properties on both, also known as a Property Graph. It is a high performance graph store with all the features expected of a mature and robust database, like a friendly query language and ACID transactions. ...
DgraphDgraph's goal is to provide Google production level scale and throughput, with low enough latency to be serving real time user queries, over terabytes of structured data. Dgraph supports GraphQL-like query syntax, and responds in JSON and Protocol Buffers over GRPC and HTTP. ...
JanusGraphIt is a scalable graph database optimized for storing and querying graphs containing hundreds of billions of vertices and edges distributed across a multi-machine cluster. It is a transactional database that can support thousands of concurrent users executing complex graph traversals in real time. ...
RedisGraphRedisGraph is a graph database developed from scratch on top of Redis, using the new Redis Modules API to extend Redis with new commands and capabilities. Its main features include: - Simple, fast indexing and querying - Data stored in RAM, using memory-efficient custom data structures - On disk persistence - Tabular result sets - Simple and popular graph query language (Cypher) - Data Filtering, Aggregation and ordering ...
CayleyCayley is an open-source graph inspired by the graph database behind Freebase and Google's Knowledge Graph. Its goal is to be a part of the developer's toolbox where Linked Data and graph-shaped data (semantic webs, social networks, etc) in general are concerned. ...
TypeDBTypeDB is a database with a rich and logical type system. TypeDB empowers you to solve complex problems, using TypeQL as its query language. ...
Nebula GraphIt is an open source distributed graph database. It has a shared-nothing architecture and scales quite well due to the separation of storage and computation. It can handle hundreds of billions of vertices and trillions of edges while still maintaining milliseconds of latency. It is openCypher compatible. ...
TerminusDBIt is a database built for data people. Terminus is a model driven graph database designed specifically for the web-age. The result is unified, well-structured & refined data - the jet fuel of future business. It greatly reduces the time and effort required to build any application that shares, manipulates or edits data. ...
Titan alternatives & related posts
- Cypher – graph query language70
- Great graphdb61
- Open source33
- Rest api31
- High-Performance Native API27
- ACID24
- Easy setup21
- Great support17
- Clustering11
- Hot Backups9
- Great Web Admin UI8
- Mature7
- Powerful, flexible data model7
- Embeddable6
- Easy to Use and Model5
- Best Graphdb4
- Highly-available4
- Great onboarding process2
- It's awesome, I wanted to try it2
- Used by Crunchbase2
- Great query language and built in data browser2
- Comparably slow9
- Can't store a vertex as JSON4
- Doesn't have a managed cloud service at low cost1
related Neo4j posts
We have an in-house build experiment management system. We produce samples as input to the next step, which then could produce 1 sample(1-1) and many samples (1 - many). There are many steps like this. So far, we are tracking genealogy (limited tracking) in the MySQL database, which is becoming hard to trace back to the original material or sample(I can give more details if required). So, we are considering a Graph database. I am requesting advice from the experts.
- Is a graph database the right choice, or can we manage with RDBMS?
- If RDBMS, which RDMS, which feature, or which approach could make this manageable or sustainable
- If Graph database(Neo4j, OrientDB, Azure Cosmos DB, Amazon Neptune, ArangoDB), which one is good, and what are the best practices?
I am sorry that this might be a loaded question.
I'm evaluating the use of RedisGraph vs Microsoft SQL Server 2019 graph features to build a social graph. One of the key criteria is high availability and cross data center replication of data. While Neo4j is a much-matured solution in general, I'm not accounting for it due to the cost & introduction of a new stack in the ecosystem. Also, due to the nature of data & org policies, using a cloud-based solution won't be a viable choice.
We currently use Redis as a cache & SQL server 2019 as RDBMS.
I'm inclining towards SQL server 2019 graph as we already use SQL server extensively as relational database & have all the HA and cross data center replication setup readily available. I still need to evaluate if it fulfills our need as a graph DB though, I also learned that SQL server 2019 is still a new player in the market and attempts to fit a graph-like query on top of a relational model (with node and edge tables). RedisGraph seems very promising. However, I'm not totally sure about HA, Graph data backup, cross-data center support.
- Graphql as a query language is nice if you like apollo3
- Easy set up2
- Low learning curve2
- Open Source1
- High Performance1
related Dgraph posts
related JanusGraph posts
- 10x – 600x faster than any other graph database2
- Cypher – graph query language2
- Great graphdb1
- Open source1
related RedisGraph posts
I'm evaluating the use of RedisGraph vs Microsoft SQL Server 2019 graph features to build a social graph. One of the key criteria is high availability and cross data center replication of data. While Neo4j is a much-matured solution in general, I'm not accounting for it due to the cost & introduction of a new stack in the ecosystem. Also, due to the nature of data & org policies, using a cloud-based solution won't be a viable choice.
We currently use Redis as a cache & SQL server 2019 as RDBMS.
I'm inclining towards SQL server 2019 graph as we already use SQL server extensively as relational database & have all the HA and cross data center replication setup readily available. I still need to evaluate if it fulfills our need as a graph DB though, I also learned that SQL server 2019 is still a new player in the market and attempts to fit a graph-like query on top of a relational model (with node and edge tables). RedisGraph seems very promising. However, I'm not totally sure about HA, Graph data backup, cross-data center support.
- Full open source7
related Cayley posts
related TypeDB posts
related Nebula Graph posts