RedisGraph
Apache AGE
Our great sponsors
RedisGraph | Apache AGE | |
---|---|---|
5 | 31 | |
1,960 | 709 | |
0.6% | - | |
6.9 | 8.5 | |
3 days ago | over 1 year ago | |
C | C | |
GNU General Public License v3.0 or later | Apache License 2.0 |
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.
RedisGraph
-
Matrices and Graph
This approach reminds me of RedisGraph[1] (which is now unfortunately EoL).
"RedisGraph is the first queryable Property Graph database to use sparse matrices to represent the adjacency matrix in graphs and linear algebra to query the graph."
1. https://github.com/RedisGraph/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' $
Apache AGE
-
Alternatives to Neo4j Enterprise
What about the AGE extension for Postgres? https://age.apache.org/
-
Anyone Using Graph Databases in F#?
Waiting for Postgres to release theirs.
-
In MongoDB you can have duplicate items even if you have unique index
I think they are talking about the AGE extension https://age.apache.org
-
Age 1.0 – PostgreSQL extension for graph database
It's my understanding of the "incubation" period of Apache Software Foundation projects is to determine if they're able to actually execute the ASF process, and a bunch of other "project maturity metrics" (https://community.apache.org/apache-way/apache-project-matur...) of which AGE currently has some self-certification: https://age.apache.org/?l=maturity#
I recognize that's not exactly an answer to the question you asked, but I would be surprised if someone other than a project member knows a more forward-looking one
-
Looking for opinions: 95% of my Data fits extremely well in a Relational Database and 5% fits extremely well into a graph database. Should I consider splitting it between the two, or is that a silly idea?
Postgres has a graph extension: https://age.apache.org. This means you can keep all your data in PG and use both models.
-
Getting Started with Redis and RedisGraph
PostgreSQL with graph extension, developed by a team at Apache Software Foundation as Apache AGE. Apache AGE uses Gremlin.
-
Ask HN: Why are relational DBs are the standard instead of graph-based DBs?
The big thing that graph dbs provide is transitive traversals of join relationships.
The problem with graph dbs is trying to return something that is not a graph. Like a count. Or derived information. And which graph model do you use? There’s more than one. Lots of information is very poorly modeled in graph dbs. Temporal organization, for example.
Ultimately, graphs are a way to use relations. But relations allow you much more flexibility to associate information (subject to the issue of transitive relationship traversal).
Mixed graph-relational is perfectly reasonable. Reasonable start here: [https://age.apache.org/]
their actual landing page is actually better than the Github one. It's a translation layer(s) to allow querying Postgres using openCypher
-
Truth Behind Neo4j’s “Trillion” Relationship Graph
Depending on how one views "postgres", there are at least two extensions that allegedly do it: https://age.apache.org/ and the AgensGraph from which AGE derives
-
One table vs two table design
There's an extension to postgresql (I haven't used it, but I am familiar with node/edge tables in MSSQL) that allows you to do this: https://age.apache.org/
What are some alternatives?
Neo4j - Graphs for Everyone
janusgraph - JanusGraph: an open-source, distributed graph database
PostgreSQL - Mirror of the official PostgreSQL GIT repository. Note that this is just a *mirror* - we don't work with pull requests on github. To contribute, please see https://wiki.postgresql.org/wiki/Submitting_a_Patch
yugabyte-db - YugabyteDB - the cloud native distributed SQL database for mission-critical applications.
RedisInsight - Redis GUI by Redis
datalevin - A simple, fast and versatile Datalog database
RedisTimeSeries - Time Series data structure for Redis
datahike - A durable Datalog implementation adaptable for distribution.
RediSearch - A query and indexing engine for Redis, providing secondary indexing, full-text search, vector similarity search and aggregations.
datascript - Immutable database and Datalog query engine for Clojure, ClojureScript and JS