News for hackers. Stuff that matters.
Re:Max Datom: Interactive Datomic Tutorial by emccue on Friday April 22, 2022 @11:45AM (#31123079)
If anyone is interested, I am attempting to revive an open source clone of Datomic called EVA.

As is the original codebase works fine, its just unmaintained. My hope is to clean up the code, make an HTTP layer for a remote peer, and make a Rust embedded peer so that this sort of Database can finally escape the JVM.

https://github.com/bowbahdoe/eva

If you want to use something open source today that has the same query language but a different data model, https://xtdb.com/ is high quality.

Re:Max Datom: Interactive Datomic Tutorial by panick21_ on Friday April 22, 2022 @11:52AM (#31123207)
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

Re:Max Datom: Interactive Datomic Tutorial by emccue on Friday April 22, 2022 @12:13PM (#31123534)
Feel free to reach out via any of the contact info on my github. The more the merrier chasing this magic dragon.
Re:Max Datom: Interactive Datomic Tutorial by den1k on Friday April 22, 2022 @02:20PM (#31125854)
if you don't need history, have a look at https://github.com/juji-io/datalevin
Re:Max Datom: Interactive Datomic Tutorial by emccue on Friday April 22, 2022 @04:41PM (#31127793)
Datalevin is good, but its more useful in the same realm as sqlite
Re:Max Datom: Interactive Datomic Tutorial by huahaiy on Thursday April 28, 2022 @03:03PM (#31196798)
Not exactly.

My goal of developing Datalevin is to replace our use of both Datomic and Postgres, so we have a single DB. The aim is to provide a versatile database that meets data needs of most use cases.

I mention Sqlite in README because I have not finished the query engine rewrite of Datalevin, so the query performance is not up to my standard of being competitive with relational databases for large data sets. However, even at the current state, Datalevin is already faster than the alternative Datalog stores in the Clojure world for the most part.

Finally, since you seems to want to go into this space, I will mention that: without some new tricks in query algorithms, triple stores would be always slower than standard relational DBs. This is not a solved problem. Just be aware what you are getting yourself into.