Comment by spiffytech
10 hours ago
Since Marmot pivoted to the MySQL wire protocol, I haven't had a clear picture of its advantages over using normal MySQL with active-active replication. Can you speak to that?
10 hours ago
Since Marmot pivoted to the MySQL wire protocol, I haven't had a clear picture of its advantages over using normal MySQL with active-active replication. Can you speak to that?
Here are some that I can think on top of my head:
- Marmot let's you choose consistency level (ONE/QUORUM/FULL) vs MySQL's serializable.
- MySQL requires careful setup of replication, conflict avoidance and monitoring. Fencing split brain and failover is manual in many cases. Marmot even right now is easier to spin up, plus it's leaderless. So you can actually just have your client talk to different nodes (maybe in round robin fashion) to do load distribution.
- Marmot's eventual consistency + anti-entropy will recover brain-splits with you requiring to do anything. MySQL active active requires manual ops.
- Marmot's designed for read-heavy on the edge scenarios. Once I've completed the read-only replica system you can literally bring up or down lambda nodes with Marmot running as sidecar. With replicas being able to select DBs they want (WIP) you should be able to bring up region/org/scenario specific servers with their light weight copies, and writes will be proxied to main server. Applications are virtually unlimited. Since you can directly read SQLite database, think many small vector databases distributed to edge, or regional configurations, or catalogs.