[bhouston]

I have tried this before:

https://www.dolthub.com/

It was a lot of work and had poor performance with a lot of complications. I am not using it in my latest projects as a result.

[zachmu]

Can you be more specific about what complications you ran into? As for performance, Dolt is faster overall than MySQL on sysbench now.

https://docs.dolthub.com/sql-reference/benchmarks/latency

[bhouston]

It was https://threekit.com. It was a while ago now but we had to use MySQL for our primary copy that users used (e.g. prod), and only when they were working on branches did we use dolt. I think the second complication was that Dolt was not stable enough to use in heavy load scenarios as well.

I can delete this comment if you do not want to discuss this publicly.

[zachmu]

I remember that engineering decision. You guys were pretty early customers for your throughput and durability requirements (we hadn't even added standby replication yet when you started your integration). We've come a long way in the years since then.

[timsehn]

Thanks for being an early adopter. We learned a lot trying to support your use case and you’re still customers so it can’t have been too bad…

[evdubs]

I, too, have used it. It works well and is especially great for data sharing.

[johnthescott]

makes sense. i can see things getting complex very quickly.

seems most versions would be better managed at application level, zfs/btrs snapshots not withstanding.