Neo4j
RedisGraph
Our great sponsors
Neo4j | RedisGraph | |
---|---|---|
49 | 5 | |
12,351 | 1,957 | |
1.4% | 0.9% | |
9.9 | 8.2 | |
3 days ago | 4 months ago | |
Java | C | |
GNU General Public License v3.0 only | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Neo4j
-
How to choose the right type of database
Neo4j: An ACID-compliant graph database with a high-performance distributed architecture. Ideal for complex relationship and pattern analysis in domains like social networks.
-
Looks Like the Free Software Foundation Forced Neo4j's Hand
After spending millions fighting the committer of ONgDB who removed the commons clause from the AGPL branded license, it looks like the Free Software Foundation got involved and forced them to remove the commons clause or change the license to their own proprietary license.
https://github.com/neo4j/neo4j/commit/b6237ca4e31706b1efbd0f...
-
Getting Started with GenAI Stack powered with Docker, LangChain, Neo4j and Ollama
The GenAI Stack came about through a collaboration between Docker, Neo4j, LangChain, and Ollama. The goal of the collaboration was to create a pre-built GenAI stack of best-in-class technologies that are well integrated, come with sample applications, and make it easy for developers to get up and running. The goal of the collaboration was to create a pre-built GenAI stack of best-in-class technologies that are well integrated, come with sample applications, and make it easy for developers to get up and running.
-
Database Review: Top Five Missing Features from Database APIs
Neo4j (GraphQL)
-
How to Choose the Right Document-Oriented NoSQL Database for Your Application
NoSQL is a term that we have become very familiar with in recent times and it is used to describe a set of databases that don't make use of SQL when writing & composing queries. There are loads of different types of NoSQL databases ranging from key-value databases like the Reddis to document-oriented databases like MongoDB and Firestore to graph databases like Neo4J to multi-paradigm databases like FaunaDB and Cassandra.
-
Loading data
this thread on this github issue could be useful.
-
[For Hire] Senior Developer with 14 years experience. Canadian expat in a low cost of living country | From 500 EUR per project/month
Recently I have taken an interest in big data. https://neo4j.com/ , https://cassandra.apache.org/ , https://clickhouse.com/, https://www.elastic.co/ - are all databases I have experience with. Neo4j and Cassandra only as a hobby, but Clickhouse I have used in production, and Elasticsearch I have used for some 7 years now.
-
SQL Versus NoSQL Databases: Which to Use, When, and Why
For organizations and their applications that are designed to detect fraud, like International Consortium of Investigative Journalists, or try to improve customer experience via personalization, as in the case of Tourism Media, a NoSQL graph database like Neo4j is a good match. In these kinds of use cases, the quantity of data we're dealing with is enormous, and the pattern we're searching for in the data is often complex.
-
Graph Databases vs Relational Databases: What and why?
First, you need to choose a specific graph database platform to work with, such as Neo4j, OrientDB, JanusGraph, Arangodb or Amazon Neptune. Once you have selected a platform, you can then start working with graph data using the platform's query language.
RedisGraph
-
Is BDD alive in C++ ?
It's also my impression that redis-graph uses Gherkin (the language of Cucumber) while the redis server relies on Tcl for testing. So is Tcl is a valid choice for BDD in C++ ? (redis is C, but any such framework would immediately be transferable).
-
BTC onchain analysis (Redis Hackathon)
Redis - Graph
-
A Dating Tool for Returning Inmates
So that we don’t give an ex-inmate the option of crime, let’s get them reintegrated into society faster. Dating a person who has also been in the system could be a faster way to achieve that. To matchmake both entities, we need to consider their peculiar dating interests. The more data we have for these interests, the more we can give the perfect match. Usually, when building a social tool that involves complex relationships amongst entities, it is recommended to use a graph database such as RedisGraph. We may explore this later as we progress. But not to complicate things, for now, we would rather store these interests coming from various Omni-channels such as social media, sms, online forms, text, etc. in JSON. Often, this is the first step of the data analysis process known as data collection.
-
Getting Started with Redis and RedisGraph
$ git clone https://github.com/RedisGraph/RedisGraph -b v2.4.11 --recurse-submodules -j8 Cloning into 'RedisGraph'... remote: Enumerating objects: 49063, done. remote: Counting objects: 100% (2906/2906), done. remote: Compressing objects: 100% (1082/1082), done. remote: Total 49063 (delta 1998), reused 2448 (delta 1736), pack-reused 46157 Receiving objects: 100% (49063/49063), 39.33 MiB | 114.00 KiB/s, done. Resolving deltas: 100% (38402/38402), done. Submodule 'deps/RediSearch' (https://github.com/RediSearch/RediSearch.git) registered for path 'deps/RediSearch' Submodule 'deps/googletest' (https://github.com/google/googletest.git) registered for path 'deps/googletest' Submodule 'deps/libcypher-parser' (https://github.com/RedisGraph/libcypher-parser.git) registered for path 'deps/libcypher-parser' Submodule 'deps/rax' (https://github.com/antirez/rax.git) registered for path 'deps/rax' Submodule 'deps/readies' (https://github.com/RedisLabsModules/readies.git) registered for path 'deps/readies' Submodule 'deps/xxHash' (https://github.com/Cyan4973/xxHash.git) registered for path 'deps/xxHash' Cloning to '/home/bpdp/master/postdoc-ugm/RedisGraph/deps/RediSearch'... remote: Enumerating objects: 34395, done. remote: Counting objects: 100% (1802/1802), done. remote: Compressing objects: 100% (1097/1097), done. remote: Total 34395 (delta 1150), reused 1182 (delta 696), pack-reused 32593 Receiving objects: 100% (34395/34395), 23.62 MiB | 71.00 KiB/s, done. Resolving deltas: 100% (25261/25261), done. Cloning to '/home/bpdp/master/postdoc-ugm/RedisGraph/deps/rax'... remote: Enumerating objects: 668, done. remote: Counting objects: 100% (25/25), done. remote: Compressing objects: 100% (14/14), done. remote: Total 668 (delta 12), reused 19 (delta 11), pack-reused 643 Receiving objects: 100% (668/668), 236.14 KiB | 1.41 MiB/s, done. Resolving deltas: 100% (414/414), done. Cloning to '/home/bpdp/master/postdoc-ugm/RedisGraph/deps/readies'... remote: Enumerating objects: 2354, done. remote: Counting objects: 100% (833/833), done. remote: Compressing objects: 100% (329/329), done. remote: Total 2354 (delta 608), reused 675 (delta 503), pack-reused 1521 Receiving objects: 100% (2354/2354), 390.69 KiB | 17.00 KiB/s, done. Resolving deltas: 100% (1577/1577), done. Cloning to '/home/bpdp/master/postdoc-ugm/RedisGraph/deps/libcypher-parser'... remote: Enumerating objects: 3250, done. remote: Counting objects: 100% (68/68), done. remote: Compressing objects: 100% (46/46), done. remote: Total 3250 (delta 42), reused 43 (delta 21), pack-reused 3182 Receiving objects: 100% (3250/3250), 2.10 MiB | 28.00 KiB/s, done. Resolving deltas: 100% (2488/2488), done. Cloning to '/home/bpdp/master/postdoc-ugm/RedisGraph/deps/xxHash'... remote: Enumerating objects: 4784, done. remote: Counting objects: 100% (345/345), done. remote: Compressing objects: 100% (188/188), done. remote: Total 4784 (delta 189), reused 255 (delta 143), pack-reused 4439 Receiving objects: 100% (4784/4784), 2.54 MiB | 27.00 KiB/s, done. Resolving deltas: 100% (2922/2922), done. Cloning to '/home/bpdp/master/postdoc-ugm/RedisGraph/deps/googletest'... remote: Enumerating objects: 23334, done. remote: Counting objects: 100% (234/234), done. remote: Compressing objects: 100% (142/142), done. remote: Total 23334 (delta 120), reused 146 (delta 81), pack-reused 23100 Receiving objects: 100% (23334/23334), 9.49 MiB | 44.00 KiB/s, done. Resolving deltas: 100% (17191/17191), done. Submodule path 'deps/RediSearch': checked out '68430b3c838374478dd9ffe4e361534f572b16ff' Submodule 'deps/googletest' (https://github.com/google/googletest.git) registered for path 'deps/RediSearch/deps/googletest' Submodule 'deps/readies' (https://github.com/RedisLabsModules/readies.git) registered for path 'deps/RediSearch/deps/readies' Cloning to '/home/bpdp/master/postdoc-ugm/RedisGraph/deps/RediSearch/deps/googletest'... remote: Enumerating objects: 23334, done. remote: Counting objects: 100% (234/234), done. remote: Compressing objects: 100% (148/148), done. remote: Total 23334 (delta 120), reused 141 (delta 75), pack-reused 23100 Receiving objects: 100% (23334/23334), 9.56 MiB | 1.05 MiB/s, done. Resolving deltas: 100% (17185/17185), done. Kloning ke '/home/bpdp/master/postdoc-ugm/RedisGraph/deps/RediSearch/deps/readies'... remote: Enumerating objects: 2354, done. remote: Counting objects: 100% (833/833), done. remote: Compressing objects: 100% (329/329), done. remote: Total 2354 (delta 608), reused 675 (delta 503), pack-reused 1521 Receiving objects: 100% (2354/2354), 390.69 KiB | 853.00 KiB/s, done. Resolving deltas: 100% (1577/1577), done. Submodule path 'deps/RediSearch/deps/googletest': checked out 'dea0216d0c6bc5e63cf5f6c8651cd268668032ec' Submodule path 'deps/RediSearch/deps/readies': checked out '89be267427c7dfcfaab4064942ef0f595f6b1fa3' Submodule path 'deps/googletest': checked out '565f1b848215b77c3732bca345fe76a0431d8b34' Submodule path 'deps/libcypher-parser': checked out '38cdee1867b18644616292c77fe2ac1f2b179537' Submodule path 'deps/rax': checked out 'ba4529f6c836c9ff1296cde12b8557329f5530b7' Submodule path 'deps/readies': checked out 'd59f3ad4e9b3d763eb41df07567111dc94c6ecac' Submodule path 'deps/xxHash': checked out '726c14000ca73886f6258a6998fb34dd567030e9' $
What are some alternatives?
Apache AGE - Graph database optimized for fast analysis and real-time data processing. It is provided as an extension to PostgreSQL. [Moved to: https://github.com/apache/age]
Hasura - Blazing fast, instant realtime GraphQL APIs on your DB with fine grained access control, also trigger webhooks on database events.
FlockDB - A distributed, fault-tolerant graph database
ArangoDB - 🥑 ArangoDB is a native multi-model database with flexible data models for documents, graphs, and key-values. Build high performance applications using a convenient SQL-like query language or JavaScript extensions.
janusgraph - JanusGraph: an open-source, distributed graph database
dbt-databricks - A dbt adapter for Databricks.
TypeGraphQL - Create GraphQL schema and resolvers with TypeScript, using classes and decorators!
supabase - The open source Firebase alternative.
MongoDB - The MongoDB Database
NebulaGraph Database - A distributed, fast open-source graph database featuring horizontal scalability and high availability
graphql-shield - 🛡 A GraphQL tool to ease the creation of permission layer.