Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Neo4j

1.2K
1.4K
+ 1
351
Presto

394
1K
+ 1
66
Add tool

Neo4j vs Presto: What are the differences?

<Write Introduction here>
  1. Data Model: Neo4j is a graph database that stores data in nodes connected by relationships, allowing for complex relationships to be easily represented. On the other hand, Presto is a distributed SQL query engine for big data that does not have a native graph data model, making it more suitable for traditional relational and columnar data.

  2. Query Language: Neo4j uses Cypher, a graph query language designed specifically for graph databases, allowing users to write expressive queries for traversing the graph data. In contrast, Presto uses SQL as its query language, enabling users familiar with SQL to work with diverse data sources efficiently.

  3. Scalability: Neo4j is a NoSQL database that provides low latency and high availability by distributing data across multiple servers, but it may be limited in scalability for massive datasets. Presto, being a distributed query engine, can scale horizontally to handle large volumes of data through parallel processing across a cluster of machines.

  4. Use Case: Neo4j is ideal for applications that require intricate relationship mapping, such as social networks, recommendations, and fraud detection, where relationships are crucial in the data model. Presto, on the other hand, is suitable for analytical queries on large datasets where real-time analysis and interactive querying are needed without the complexity of graph traversal.

  5. Architecture: Neo4j is designed as a native graph database, where data is stored in the form of nodes and relationships, optimized for graph processing. In contrast, Presto follows a shared-nothing architecture, where each node communicates independently to serve queries, enabling better scalability and resource utilization for distributed querying.

  6. Community Support: Neo4j has a strong community focused on graph database applications, providing extensive resources, plugins, and support for developers working with graph data. Presto, originally developed by Facebook and now under the Presto Software Foundation, has a growing community specializing in distributed data processing and analytics, ensuring continued development and enhancement of the query engine.

In Summary, Neo4j focuses on graph processing and complex relationships with Cypher as its query language, while Presto is geared towards distributed querying of large datasets using SQL. Both have distinct strengths and are suited for different use cases.
Decisions about Neo4j and Presto
Ashish Singh
Tech Lead, Big Data Platform at Pinterest · | 38 upvotes · 3.4M views

To provide employees with the critical need of interactive querying, we’ve worked with Presto, an open-source distributed SQL query engine, over the years. Operating Presto at Pinterest’s scale has involved resolving quite a few challenges like, supporting deeply nested and huge thrift schemas, slow/ bad worker detection and remediation, auto-scaling cluster, graceful cluster shutdown and impersonation support for ldap authenticator.

Our infrastructure is built on top of Amazon EC2 and we leverage Amazon S3 for storing our data. This separates compute and storage layers, and allows multiple compute clusters to share the S3 data.

We have hundreds of petabytes of data and tens of thousands of Apache Hive tables. Our Presto clusters are comprised of a fleet of 450 r4.8xl EC2 instances. Presto clusters together have over 100 TBs of memory and 14K vcpu cores. Within Pinterest, we have close to more than 1,000 monthly active users (out of total 1,600+ Pinterest employees) using Presto, who run about 400K queries on these clusters per month.

Each query submitted to Presto cluster is logged to a Kafka topic via Singer. Singer is a logging agent built at Pinterest and we talked about it in a previous post. Each query is logged when it is submitted and when it finishes. When a Presto cluster crashes, we will have query submitted events without corresponding query finished events. These events enable us to capture the effect of cluster crashes over time.

Each Presto cluster at Pinterest has workers on a mix of dedicated AWS EC2 instances and Kubernetes pods. Kubernetes platform provides us with the capability to add and remove workers from a Presto cluster very quickly. The best-case latency on bringing up a new worker on Kubernetes is less than a minute. However, when the Kubernetes cluster itself is out of resources and needs to scale up, it can take up to ten minutes. Some other advantages of deploying on Kubernetes platform is that our Presto deployment becomes agnostic of cloud vendor, instance types, OS, etc.

#BigData #AWS #DataScience #DataEngineering

See more
Karthik Raveendran
CPO at Attinad Software · | 3 upvotes · 221.1K views

The platform deals with time series data from sensors aggregated against things( event data that originates at periodic intervals). We use Cassandra as our distributed database to store time series data. Aggregated data insights from Cassandra is delivered as web API for consumption from other applications. Presto as a distributed sql querying engine, can provide a faster execution time provided the queries are tuned for proper distribution across the cluster. Another objective that we had was to combine Cassandra table data with other business data from RDBMS or other big data systems where presto through its connector architecture would have opened up a whole lot of options for us.

See more
Manage your open source components, licenses, and vulnerabilities
Learn More
Pros of Neo4j
Pros of Presto
  • 69
    Cypher – graph query language
  • 61
    Great graphdb
  • 33
    Open source
  • 31
    Rest api
  • 27
    High-Performance Native API
  • 23
    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
    It's awesome, I wanted to try it
  • 2
    Great onboarding process
  • 2
    Great query language and built in data browser
  • 2
    Used by Crunchbase
  • 18
    Works directly on files in s3 (no ETL)
  • 13
    Open-source
  • 12
    Join multiple databases
  • 10
    Scalable
  • 7
    Gets ready in minutes
  • 6
    MPP

Sign up to add or upvote prosMake informed product decisions

Cons of Neo4j
Cons of Presto
  • 9
    Comparably slow
  • 4
    Can't store a vertex as JSON
  • 1
    Doesn't have a managed cloud service at low cost
    Be the first to leave a con

    Sign up to add or upvote consMake informed product decisions

    263
    642
    22.9K
    19
    79
    3.2K
    - No public GitHub repository available -

    What is 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.

    What is Presto?

    Distributed SQL Query Engine for Big Data

    Need advice about which tool to choose?Ask the StackShare community!

    Jobs that mention Neo4j and Presto as a desired skillset
    What companies use Neo4j?
    What companies use Presto?
    Manage your open source components, licenses, and vulnerabilities
    Learn More

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with Neo4j?
    What tools integrate with Presto?

    Sign up to get full access to all the tool integrationsMake informed product decisions

    What are some alternatives to Neo4j and Presto?
    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.
    MongoDB
    MongoDB stores data in JSON-like documents that can vary in structure, offering a dynamic, flexible schema. MongoDB was also designed for high availability and scalability, with built-in replication and auto-sharding.
    Cassandra
    Partitioning means that Cassandra can distribute your data across multiple machines in an application-transparent matter. Cassandra will automatically repartition as machines are added and removed from the cluster. Row store means that like relational databases, Cassandra organizes data by rows and columns. The Cassandra Query Language (CQL) is a close relative of SQL.
    OrientDB
    It is an open source NoSQL database management system written in Java. It is a Multi-model database, supporting graph, document, key/value, and object models, but the relationships are managed as in graph databases with direct connections between records.
    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.
    See all alternatives