Question 1

Duratom vs enduro: which should I use for Clojure?

Accepted Answer

Duratom is a drop-in replacement for Clojure atoms with full interface support, while enduro requires custom swap! and reset! calls. Choose duratom for seamless integration; enduro if you prefer its specific architecture and don't need standard atom compatibility.

Question 2

How to set up duratom with PostgreSQL for production?

Accepted Answer

Use the :postgres-db backend with clojure.java.jdbc db-spec, table name, and row ID. Consider adding Nippy serialization for efficiency and enabling synchronous commits if immediate consistency is required, as per the documentation.

Question 3

Can duratom handle failures when persisting to S3?

Accepted Answer

Yes, configure an :error-handler in the :rw map to catch exceptions and optionally retry commits. In synchronous mode or with duragent, recommits are safe; otherwise, state may have changed before retry.

Question 4

What's the performance impact of using duratom with Redis?

Accepted Answer

It adds overhead from serialization and network calls, and state exists twice in memory (atom + Redis). Use async commits to minimize latency, but note Redis's in-memory nature might not guarantee durability without persistence settings.

Question 5

How to migrate from regular atoms to duratom without breaking code?

Accepted Answer

Simply replace atom constructors with duratom calls using the same interfaces—swap! and reset! work identically. Start with a local file backend for testing, then switch to production storage like PostgreSQL.

Question 6

Does duratom support transactions across multiple atoms?

Accepted Answer

No, it focuses on single-atom durability. For multi-atom transactions, you'd need to coordinate externally using Clojure's refs or STM, combined with duratom for persistence, which adds complexity.

Duratom

What is Duratom?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions