Hacker News Reader

This is a large part of what Rich Hickey emphasizes about Datomic, too. We're so used to the database being "over there" but it's actually very nice to have it locally. Datomic solves this in the context of a distributed database by having the read-only replicas local to client applications while the transaction-running parts are remote.

View on HN

Only trouble with that particular implementation is that the Datomic Transactor is a single threaded single process that serializes every transaction going through it. As long as you don't need to scale writes it works like a charm. However, the workloads I somehow always end up working with are write heavy or at best 50/50 between read and write.

That's another trait it would share with SQLite + litestream, until SQLite's BEGIN CONCURRENT is released.

It's exciting to see Datomic's architecture realized using more conventional technology.

Reply on news.ycombinator.com