Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.
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. | It is an open source library of graph-theoretic data structures and algorithms. It has been used in a number of university projects and classes, and shows up as a standard reference in books on Java programming. |
intuitive, using a graph model for data representation;reliable, with full ACID transactions;durable and fast, using a custom disk-based, native storage engine;massively scalable, up to several billion nodes/relationships/properties;highly-available, when distributed across multiple machines;expressive, with a powerful, human readable graph query language;fast, with a powerful traversal framework for high-speed graph queries;embeddable, with a few small jars;simple, accessible by a convenient REST interface or an object-oriented Java API | Flexible;
Powerfull;
Efficient |
Statistics | |
GitHub Stars 15.3K | GitHub Stars 2.7K |
GitHub Forks 2.5K | GitHub Forks 849 |
Stacks 1.2K | Stacks 8 |
Followers 1.4K | Followers 15 |
Votes 351 | Votes 0 |
Pros & Cons | |
Pros
Cons
| No community feedback yet |
Integrations | |
| No integrations available | |

It tailors your application for GraalVM and HotSpot. Amazingly fast boot time, incredibly low RSS memory (not just heap size!) offering near instant scale up and high density memory utilization in container orchestration platforms like Kubernetes. We use a technique we call compile time boot.

It is a first class persistence framework with support for custom SQL, stored procedures and advanced mappings. It eliminates almost all of the JDBC code and manual setting of parameters and retrieval of results. It can use simple XML or Annotations for configuration and map primitives, Map interfaces and Java POJOs (Plain Old Java Objects) to database records.

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.

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

The Guava project contains several of Google's core libraries that we rely on in our Java-based projects: collections, caching, primitives support, concurrency libraries, common annotations, string processing, I/O, and so forth.

It is a modern server-side Java template engine for both web and standalone environments. It is aimed at creating elegant web code while adding powerful features and retaining prototyping abilities.

It is used for building component-based user interfaces for web applications and was formalized as a standard through the Java Community

It is a fully open-source high-performance graph database supporting the RDF data model and RDR. It operates as an embedded database or over a client/server REST API.

It is used to monitor Java or Java EE application servers in QA and production environments. It is not a tool to simulate requests from users, it is a tool to measure and calculate statistics on real operation of an application depending on the usage of the application by users. It is mainly based on statistics of requests and on evolution charts.