Alternatives to Neo4j logo

Alternatives to Neo4j

Titan, MongoDB, Cassandra, OrientDB, and JanusGraph are the most popular alternatives and competitors to Neo4j.
566
493
+ 1
284

What is Neo4j and what are its top alternatives?

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.
Neo4j is a tool in the Graph Databases category of a tech stack.
Neo4j is an open source tool with 7.4K GitHub stars and 1.8K GitHub forks. Here’s a link to Neo4j's open source repository on GitHub

Neo4j alternatives & related posts

Titan logo

Titan

29
18
0
29
18
+ 1
0
Distributed Graph Database
    Be the first to leave a pro
    Titan logo
    Titan
    VS
    Neo4j logo
    Neo4j
    MongoDB logo

    MongoDB

    21.1K
    17.6K
    3.9K
    21.1K
    17.6K
    + 1
    3.9K
    The database for giant ideas
    MongoDB logo
    MongoDB
    VS
    Neo4j logo
    Neo4j

    related MongoDB posts

    Jeyabalaji Subramanian
    Jeyabalaji Subramanian
    CTO at FundsCorner · | 24 upvotes · 726.6K views
    atFundsCornerFundsCorner
    MongoDB
    MongoDB
    PostgreSQL
    PostgreSQL
    MongoDB Stitch
    MongoDB Stitch
    Node.js
    Node.js
    Amazon SQS
    Amazon SQS
    Python
    Python
    SQLAlchemy
    SQLAlchemy
    AWS Lambda
    AWS Lambda
    Zappa
    Zappa

    Recently we were looking at a few robust and cost-effective ways of replicating the data that resides in our production MongoDB to a PostgreSQL database for data warehousing and business intelligence.

    We set ourselves the following criteria for the optimal tool that would do this job: - The data replication must be near real-time, yet it should NOT impact the production database - The data replication must be horizontally scalable (based on the load), asynchronous & crash-resilient

    Based on the above criteria, we selected the following tools to perform the end to end data replication:

    We chose MongoDB Stitch for picking up the changes in the source database. It is the serverless platform from MongoDB. One of the services offered by MongoDB Stitch is Stitch Triggers. Using stitch triggers, you can execute a serverless function (in Node.js) in real time in response to changes in the database. When there are a lot of database changes, Stitch automatically "feeds forward" these changes through an asynchronous queue.

    We chose Amazon SQS as the pipe / message backbone for communicating the changes from MongoDB to our own replication service. Interestingly enough, MongoDB stitch offers integration with AWS services.

    In the Node.js function, we wrote minimal functionality to communicate the database changes (insert / update / delete / replace) to Amazon SQS.

    Next we wrote a minimal micro-service in Python to listen to the message events on SQS, pickup the data payload & mirror the DB changes on to the target Data warehouse. We implemented source data to target data translation by modelling target table structures through SQLAlchemy . We deployed this micro-service as AWS Lambda with Zappa. With Zappa, deploying your services as event-driven & horizontally scalable Lambda service is dumb-easy.

    In the end, we got to implement a highly scalable near realtime Change Data Replication service that "works" and deployed to production in a matter of few days!

    See more
    Robert Zuber
    Robert Zuber
    CTO at CircleCI · | 22 upvotes · 545K views
    atCircleCICircleCI
    MongoDB
    MongoDB
    PostgreSQL
    PostgreSQL
    Redis
    Redis
    GitHub
    GitHub
    Amazon S3
    Amazon S3

    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
    Cassandra logo

    Cassandra

    2.5K
    2K
    454
    2.5K
    2K
    + 1
    454
    A partitioned row store. Rows are organized into tables with a required primary key.
    Cassandra logo
    Cassandra
    VS
    Neo4j logo
    Neo4j

    related Cassandra posts

    Thierry Schellenbach
    Thierry Schellenbach
    CEO at Stream · | 17 upvotes · 246.9K views
    atStreamStream
    Redis
    Redis
    Cassandra
    Cassandra
    RocksDB
    RocksDB
    #InMemoryDatabases
    #DataStores
    #Databases

    1.0 of Stream leveraged Cassandra for storing the feed. Cassandra is a common choice for building feeds. Instagram, for instance started, out with Redis but eventually switched to Cassandra to handle their rapid usage growth. Cassandra can handle write heavy workloads very efficiently.

    Cassandra is a great tool that allows you to scale write capacity simply by adding more nodes, though it is also very complex. This complexity made it hard to diagnose performance fluctuations. Even though we had years of experience with running Cassandra, it still felt like a bit of a black box. When building Stream 2.0 we decided to go for a different approach and build Keevo. Keevo is our in-house key-value store built upon RocksDB, gRPC and Raft.

    RocksDB is a highly performant embeddable database library developed and maintained by Facebook’s data engineering team. RocksDB started as a fork of Google’s LevelDB that introduced several performance improvements for SSD. Nowadays RocksDB is a project on its own and is under active development. It is written in C++ and it’s fast. Have a look at how this benchmark handles 7 million QPS. In terms of technology it’s much more simple than Cassandra.

    This translates into reduced maintenance overhead, improved performance and, most importantly, more consistent performance. It’s interesting to note that LinkedIn also uses RocksDB for their feed.

    #InMemoryDatabases #DataStores #Databases

    See more
    Laravel
    Laravel
    Zend Framework
    Zend Framework
    MySQL
    MySQL
    MongoDB
    MongoDB
    Cassandra
    Cassandra
    React
    React
    AngularJS
    AngularJS
    jQuery
    jQuery
    Docker
    Docker
    Linux
    Linux

    React AngularJS jQuery

    Laravel Zend Framework

    MySQL MongoDB Cassandra

    Docker

    Linux

    See more
    OrientDB logo

    OrientDB

    30
    14
    10
    30
    14
    + 1
    10
    An open source NoSQL database management system
    OrientDB logo
    OrientDB
    VS
    Neo4j logo
    Neo4j
    JanusGraph logo

    JanusGraph

    11
    14
    0
    11
    14
    + 1
    0
    Open-source, distributed graph database
      Be the first to leave a pro
      JanusGraph logo
      JanusGraph
      VS
      Neo4j logo
      Neo4j
      Dgraph logo

      Dgraph

      39
      58
      3
      39
      58
      + 1
      3
      Fast, Distributed Graph DB
      Dgraph logo
      Dgraph
      VS
      Neo4j logo
      Neo4j
      Neptune logo

      Neptune

      0
      0
      0
      0
      0
      + 1
      0
      The most lightweight experiment tracking tool for machine learning
        Be the first to leave a pro
        Neptune logo
        Neptune
        VS
        Neo4j logo
        Neo4j