Question 1

How does CubDB compare to Mnesia for Elixir?

Accepted Answer

CubDB offers stronger ACID guarantees and crash resilience with its append-only design, while Mnesia provides built-in distribution and replication but with eventual consistency in some modes. CubDB is better for standalone, robust storage, whereas Mnesia suits distributed Erlang/OTP applications.

Question 2

How to compact a CubDB database to save disk space?

Accepted Answer

Use the `CubDB.compact/1` function manually or configure automatic compaction via startup options. Compaction rewrites the B-tree to remove old versions, but it requires exclusive access and can be resource-intensive during the process.

Question 3

Is CubDB good for caching in Phoenix applications?

Accepted Answer

Yes, CubDB can serve as a persistent cache due to its fast reads and MVCC, but it's disk-based, so for pure in-memory caching, ETS might be faster. It's ideal for caches needing crash recovery and ACID properties.

Question 4

What are the performance implications of MVCC in CubDB?

Accepted Answer

MVCC allows concurrent reads and writes without blocking, improving performance in read-heavy scenarios. However, the append-only structure can lead to write amplification over time, potentially slowing writes until compaction.

Question 5

Can CubDB handle large datasets efficiently?

Accepted Answer

CubDB can manage large datasets, but performance may degrade if compaction is not regular. The immutable B-tree ensures consistency, but write operations can slow as the log grows, so monitoring and compaction are key.

Question 6

Does CubDB support encryption for sensitive data?

Accepted Answer

No, CubDB does not include built-in encryption; data is stored in plain text files. For encryption, implement it at the application level by encrypting values before storage using Elixir libraries.

cubdb

What is cubdb?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions