Apache AGE
datahike
Apache AGE | datahike | |
---|---|---|
31 | 12 | |
709 | 1,581 | |
- | 0.4% | |
8.5 | 5.9 | |
over 1 year ago | 2 days ago | |
C | Clojure | |
Apache License 2.0 | Eclipse Public License 1.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.
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/
datahike
-
The Ten Rules of Schema Growth
Datahike [0] provides similar functionality to datomic and is open source. It lacks some features however that Datomic does have [1].
[0]: https://github.com/replikativ/datahike
-
Is Datomic right for my use case?
You can also consider other durable Datalog options like datahike or datalevin which can work either as lib (SQLite style) or in a client-server setup; if you want to play with bi-temporality XTDB is a rock solid option with very good support and documentation.
- datahike for reagent SPA?
-
Open source Datomic?
Check https://github.com/replikativ/datahike
-
Max Datom: Interactive Datomic Tutorial
Oh really interesting. I didn't know about that. I was actually going threw the old Mendat code base and was considering using that.
I would really like a pure Rust version of Datomic for embed use cases.
There is all also Datahike, that is going in that direction too. It is maintained and actively developed.
https://github.com/replikativ/datahike
-
Show HN: Matrix-CRDT – real-time collaborative apps using Matrix as backend
Having an Datomic like store backed by something like this.
https://github.com/replikativ/datahike
Is an Open Source variant of Datomic.
Lambdaforge wants to eventually have this work with CRDTs.
Using the Matrix ecosystem for this is quite interesting as it solves many problems for you already.
-
Ask HN: Why are relational DBs are the standard instead of graph-based DBs?
Unlike some other commenters, I agree that graph models are usually a better fit for most data than relational models. There's been some interesting work in recent years developing this idea: in the Clojure world there's Datomic, XTDB, and a host of competitors, all of which build on work from Semantic Web/SPARQL/triplestores and logic programming. Some are even intended to be used as primary datastores: they support some amount of schema and constraints, have well-defined consistency and ACID guarantees, etc. This makes them unlike graph databases like Neo4J and others, which fill an architectural role more like Elasticsearch as a read-optimization tool. Here's an interesting talk making a case for triple-based databases.
-
Datascript + automatic persistency
Have a look at https://github.com/replikativ/datahike and https://github.com/replikativ/datahike-postgres
-
Clojure Datalog Databases
There is now a datahike linux native image preview available: https://github.com/replikativ/datahike/releases/tag/preview
-
Functional Programming with B trees
And implemented as a full-on datastore queried via Datalog: https://github.com/replikativ/datahike
What are some alternatives?
Neo4j - Graphs for Everyone
xtdb - An immutable database for application development and time-travel data compliance, with SQL and XTQL. Developed by @juxt
janusgraph - JanusGraph: an open-source, distributed graph database
datalevin - A simple, fast and versatile Datalog database
RedisGraph - A graph database as a Redis module
datascript - Immutable database and Datalog query engine for Clojure, ClojureScript and JS
yugabyte-db - YugabyteDB - the cloud native distributed SQL database for mission-critical applications.
rss-proxy - RSS-proxy allows you to do create an RSS or ATOM feed of almost any website, just by analyzing just the static HTML structure.
asami - A graph store for Clojure and ClojureScript
terminusdb - TerminusDB is a distributed database with a collaboration model