Alternatives to Memgraph logo

Alternatives to Memgraph

Neo4j, Redis, Dgraph, JanusGraph, and Titan are the most popular alternatives and competitors to Memgraph.
4
7
+ 1
0

What is Memgraph and what are its top alternatives?

Memgraph is a streaming graph application platform that helps you wrangle your streaming data, build sophisticated models that you can query in real-time, and develop applications you never thought possible in days, not months.
Memgraph is a tool in the Graph Databases category of a tech stack.
Memgraph is an open source tool with GitHub stars and GitHub forks. Here’s a link to Memgraph's open source repository on GitHub

Top Alternatives to Memgraph

  • Neo4j
    Neo4j

    Neo4j 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. ...

  • Redis
    Redis

    Redis is an open source (BSD licensed), in-memory data structure store, used as a database, cache, and message broker. Redis provides data structures such as strings, hashes, lists, sets, sorted sets with range queries, bitmaps, hyperloglogs, geospatial indexes, and streams. ...

  • Dgraph
    Dgraph

    Dgraph'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. ...

  • JanusGraph
    JanusGraph

    It 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. ...

  • Titan
    Titan

    Titan 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. Titan is a transactional database that can support thousands of concurrent users executing complex graph traversals in real time. ...

  • RedisGraph
    RedisGraph

    RedisGraph 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 ...

  • Cayley
    Cayley

    Cayley 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. ...

  • TypeDB
    TypeDB

    TypeDB is a database with a rich and logical type system. TypeDB empowers you to solve complex problems, using TypeQL as its query language. ...

Memgraph alternatives & related posts

Neo4j logo

Neo4j

1K
1.2K
352
The world’s leading Graph Database
1K
1.2K
+ 1
352
PROS OF NEO4J
  • 70
    Cypher – graph query language
  • 61
    Great graphdb
  • 32
    Open source
  • 31
    Rest api
  • 27
    High-Performance Native API
  • 24
    ACID
  • 21
    Easy setup
  • 17
    Great support
  • 11
    Clustering
  • 9
    Hot Backups
  • 8
    Great Web Admin UI
  • 7
    Powerful, flexible data model
  • 7
    Mature
  • 6
    Embeddable
  • 5
    Easy to Use and Model
  • 4
    Highly-available
  • 4
    Best Graphdb
  • 2
    Used by Crunchbase
  • 2
    Great onboarding process
  • 2
    It's awesome, I wanted to try it
  • 2
    Great query language and built in data browser
CONS OF NEO4J
  • 5
    Comparably slow
  • 4
    Can't store a vertex as JSON
  • 1
    Doesn't have a managed cloud service at low cost

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.

  1. Is a graph database the right choice, or can we manage with RDBMS?
  2. If RDBMS, which RDMS, which feature, or which approach could make this manageable or sustainable
  3. 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.

See more

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.

See more
Redis logo

Redis

47.1K
36.2K
3.9K
Open source (BSD licensed), in-memory data structure store
47.1K
36.2K
+ 1
3.9K
PROS OF REDIS
  • 879
    Performance
  • 536
    Super fast
  • 511
    Ease of use
  • 441
    In-memory cache
  • 321
    Advanced key-value cache
  • 190
    Open source
  • 179
    Easy to deploy
  • 163
    Stable
  • 152
    Free
  • 120
    Fast
  • 40
    High-Performance
  • 39
    High Availability
  • 34
    Data Structures
  • 32
    Very Scalable
  • 23
    Replication
  • 20
    Great community
  • 19
    Pub/Sub
  • 17
    "NoSQL" key-value data store
  • 14
    Hashes
  • 12
    Sets
  • 10
    Sorted Sets
  • 9
    Lists
  • 8
    BSD licensed
  • 8
    NoSQL
  • 7
    Async replication
  • 7
    Integrates super easy with Sidekiq for Rails background
  • 7
    Bitmaps
  • 6
    Open Source
  • 6
    Keys with a limited time-to-live
  • 5
    Strings
  • 5
    Lua scripting
  • 4
    Awesomeness for Free!
  • 4
    Hyperloglogs
  • 3
    outstanding performance
  • 3
    Runs server side LUA
  • 3
    Networked
  • 3
    LRU eviction of keys
  • 3
    Written in ANSI C
  • 3
    Feature Rich
  • 3
    Transactions
  • 2
    Data structure server
  • 2
    Performance & ease of use
  • 1
    Existing Laravel Integration
  • 1
    Automatic failover
  • 1
    Easy to use
  • 1
    Object [key/value] size each 500 MB
  • 1
    Simple
  • 1
    Channels concept
  • 1
    Scalable
  • 1
    Temporarily kept on disk
  • 1
    Dont save data if no subscribers are found
  • 0
    Jk
CONS OF REDIS
  • 14
    Cannot query objects directly
  • 2
    No secondary indexes for non-numeric data types
  • 1
    No WAL

related Redis posts

Robert Zuber

We use MongoDB as our primary #datastore. Mongo's approach to replica sets enables some fantastic patterns for operations like maintenance, backups, and #ETL.

As we pull #microservices from our #monolith, we are taking the opportunity to build them with their own datastores using PostgreSQL. We also use Redis to cache data we’d never store permanently, and to rate-limit our requests to partners’ APIs (like GitHub).

When we’re dealing with large blobs of immutable data (logs, artifacts, and test results), we store them in Amazon S3. We handle any side-effects of S3’s eventual consistency model within our own code. This ensures that we deal with user requests correctly while writes are in process.

See more

I'm working as one of the engineering leads in RunaHR. As our platform is a Saas, we thought It'd be good to have an API (We chose Ruby and Rails for this) and a SPA (built with React and Redux ) connected. We started the SPA with Create React App since It's pretty easy to start.

We use Jest as the testing framework and react-testing-library to test React components. In Rails we make tests using RSpec.

Our main database is PostgreSQL, but we also use MongoDB to store some type of data. We started to use Redis  for cache and other time sensitive operations.

We have a couple of extra projects: One is an Employee app built with React Native and the other is an internal back office dashboard built with Next.js for the client and Python in the backend side.

Since we have different frontend apps we have found useful to have Bit to document visual components and utils in JavaScript.

See more
Dgraph logo

Dgraph

111
185
9
Fast, Distributed Graph DB
111
185
+ 1
9
PROS OF DGRAPH
  • 3
    Graphql as a query language is nice if you like apollo
  • 2
    Easy set up
  • 2
    Low learning curve
  • 1
    Open Source
  • 1
    High Performance
CONS OF DGRAPH
    Be the first to leave a con

    related Dgraph posts

    JanusGraph logo

    JanusGraph

    37
    81
    0
    Open-source, distributed graph database
    37
    81
    + 1
    0
    PROS OF JANUSGRAPH
      Be the first to leave a pro
      CONS OF JANUSGRAPH
        Be the first to leave a con

        related JanusGraph posts

        Titan logo

        Titan

        36
        51
        0
        Distributed Graph Database
        36
        51
        + 1
        0
        PROS OF TITAN
          Be the first to leave a pro
          CONS OF TITAN
            Be the first to leave a con

            related Titan posts

            RedisGraph logo

            RedisGraph

            27
            80
            6
            A High Performance In-Memory Graph Database as a Redis Module
            27
            80
            + 1
            6
            PROS OF REDISGRAPH
            • 2
              10x – 600x faster than any other graph database
            • 2
              Cypher – graph query language
            • 1
              Great graphdb
            • 1
              Open source
            CONS OF REDISGRAPH
              Be the first to leave a con

              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.

              See more
              Cayley logo

              Cayley

              24
              69
              6
              An open-source graph database
              24
              69
              + 1
              6
              PROS OF CAYLEY
              • 6
                Full open source
              CONS OF CAYLEY
                Be the first to leave a con

                related Cayley posts

                TypeDB logo

                TypeDB

                10
                24
                0
                A strongly typed database
                10
                24
                + 1
                0
                PROS OF TYPEDB
                  Be the first to leave a pro
                  CONS OF TYPEDB
                    Be the first to leave a con

                    related TypeDB posts