Marmot

Uses a gossip-based protocol that allows any node to accept writes, eliminating single points of failure and manual failover, as highlighted in the architecture comparison with rqlite/dqlite.

Provides full MySQL protocol support, enabling existing clients, ORMs, and applications like WordPress to work without modification, with demonstrated compatibility for functions like NOW and ON DUPLICATE KEY UPDATE.

Clients can read the local SQLite file directly for sub-millisecond latency reads, which is ideal for edge computing scenarios where performance is critical, as mentioned in the edge deployment patterns.

Offers configurable write consistency (ONE, QUORUM, ALL) allowing trade-offs between latency and durability, with QUORUM as the default balanced option for distributed transactions.

Supports Debezium-compatible Change Data Capture for publishing events to Kafka or NATS, enabling real-time data pipelines and integrations without custom code.