Apache AGE
Redis
| Apache AGE | Redis | |
|---|---|---|
| 31 | 321 | |
| 709 | 65,060 | |
| - | 1.3% | |
| 8.5 | 9.7 | |
| almost 2 years ago | 7 days ago | |
| C | C | |
| Apache License 2.0 | 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.
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/
Redis
-
Hanami and HTMX - progress bar
Hi there! I want to show off a little feature I made using hanami, htmx and a little bit of redis + sidekiq.
-
What do you want to watch next? This is why I built GoodWatch.
Data Handling: Utilizes Windmill for data pipelines, with a primary database powered by PostgreSQL. Auxiliary data storage is handled by MongoDB, with Redis for caching to optimize performance
-
Valkey Is Rapidly Overtaking Redis
One of the challenges Redis labs here have is that there's very little reason for their userbase to stay loyal to them.
antirez retired from Redis development a few years ago.
From https://github.com/redis/redis/graphs/contributors it looks like activity since he left has been mostly from people who didn't overlap with him much.
Redis Labs have not shown themselves to be outstanding stewards of the project as far as I can tell. Why shouldn't people support the fork?
-
Handling Multiple requests with Redis and Bullmq
Redis
- Redis is not "open core" (2021)
-
Software Engineering Workflow
Redis - real time data storage with different data structures in a cache
-
Redict 7.3.0, a copyleft fork of Redis, is now available
[0] https://github.com/redis/redis/blob/unstable/CONTRIBUTING.md
- It has been ten days since the last commit was pushed to Redis
-
Containerize your multi-services app with docker compose
Cache: a Redis cache
- Fix Redis Drama
What are some alternatives?
Neo4j - Graphs for Everyone
Redis - 🚀 A robust, performance-focused, and full-featured Redis client for Node.js.
janusgraph - JanusGraph: an open-source, distributed graph database
LevelDB - LevelDB is a fast key-value storage library written at Google that provides an ordered mapping from string keys to string values.
RedisGraph - A graph database as a Redis module
RabbitMQ - Open source RabbitMQ: core server and tier 1 (built-in) plugins
yugabyte-db - YugabyteDB - the cloud native distributed SQL database for mission-critical applications.
Polly - Polly is a .NET resilience and transient-fault-handling library that allows developers to express policies such as Retry, Circuit Breaker, Timeout, Bulkhead Isolation, and Fallback in a fluent and thread-safe manner. From version 6.0.1, Polly targets .NET Standard 1.1 and 2.0+.
datalevin - A simple, fast and versatile Datalog database
celery - Distributed Task Queue (development branch)
datahike - A durable Datalog implementation adaptable for distribution.
Riak - Riak is a decentralized datastore from Basho Technologies.