asami
naga
Our great sponsors
asami | naga | |
---|---|---|
6 | 2 | |
626 | 373 | |
0.6% | 0.3% | |
0.0 | 0.0 | |
about 2 years ago | about 2 years ago | |
Clojure | Clojure | |
Eclipse Public License 1.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.
asami
- Ask HN: What are some 'cool' but obscure data structures you know about?
-
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.
- Introduction to the Asami Graph Database
-
How to query Datomic, Datascript, Asami, or other graph databases
Despite the documentation that exists, I've heard many people who have been confused about how to query Datomic, Datascript, Asami, or other graph databases. So I've made an attempt at explaining it https://github.com/threatgrid/asami/wiki/Introduction
- Introduction (To Graph Databases)
-
Asami
The first Graph implementation for Asami was a simple in-memory data structure, described in my ClojureD talk. The code for this appears in asami.index. This file started much smaller (as referenced above), but has since expanded with the needs extended functionality, such as transactions, and transitive closure operations.
naga
-
Asami: Turn your JSON into a Graph in 2 Lines
As for rules, I suppose I neglected talking about that in this talk, as I was only considering it in the context of, "This is where Asami came from." The rules that integrate with Asami are in a project called Naga. I gave a talk on Naga at Clojure/conj back in 2016.
-
Asami
I was pleased with how well this worked and showed my then-boss, Craig while we waiting in an airport together. He was very interested in it and asked me if I would be prepared to develop it for Cisco. I agreed, so long as I could keep it open source, which Craig was pleased to do. Thus, Naga was born.
What are some alternatives?
datascript - Immutable database and Datalog query engine for Clojure, ClojureScript and JS
mbrainz-sample - Example queries and rules for working with the Datomic mbrainz example database
crux - General purpose bitemporal database for SQL, Datalog & graph queries. Backed by @juxt [Moved to: https://github.com/xtdb/xtdb]
datahike - A durable Datalog implementation adaptable for distribution.
Neo4j - Graphs for Everyone
datalevin - A simple, fast and versatile Datalog database
terminusdb - TerminusDB is a distributed database with a collaboration model
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]
grakn - TypeDB: the polymorphic database powered by types
tries-T9-Prediction - Its artificial intelligence algorithm of T9 mobile