datalevin VS clj-tiles

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.

There are some Clojure-ecosystems things that are pretty cool, too, that you'd probably miss going into Haskell. lacinia is an extremely cool GraphQL library, and there are a variety of interesting datalog-based datastores which are spiritual descendents of Datomic, notably xtdb (formerly crux) and datalevin. Also as noted, you can write the front-end in ClojureScript if you want to, and there are a lot of cool libraries for that as well.

There are plenty of open source Datomic Inspired databases. Check out https://github.com/juji-io/datalevin and scroll down all the way down to “Alternatives”. There was even the beginning of a rust one by Mozilla: https://github.com/mozilla/mentat

The benchmarks in question have several implementation issues, I reported them on GitHub.

https://github.com/juji-io/datalevin/issues/created_by/caval...

Highly recommend you give https://github.com/juji-io/datalevin a chance. You can use it both as a key-value and/or relational datalog store (like datomic) but it’s very simple to set up and blazing fast!

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.

Physicist here. Made a kind of Physics Puzzle Game. The Github Code proofs that you do not need a backend (in a first step you only want to read and not write external files anyway). Here is what you do: 1) Sign up to and install Github, this all important step is taken for granted by any community in any language but never taught to Phyiscists. 2) Decide to use ClojureScript for your game :-) 3) Look at and reproduce the Shadow-cljs quick start 4) Using Git, clone the Shadow-cljs browser example 5) If you do not know Emacs, install VSCode+Calva 6) Understand the following two Paredit operations in Calva: ctrl+right for ForwardSexp and ctrl+left for BackwardSexp. 7) If you come to this point, try to include reagent into the shadow-cljs example. Ask again here for help if needed.