Faut en causer avec @pierrezemb.fr ;)

Etcd is implemented on the Materia serverless architecture, inheriting the same capabilities with simulation, indexing, query planner, quota management, db backup/forking, and better scaling and performance compared to a vanilla etcd

At the end, it’s more how you deal with the transaction window, which can be an issue for both reads and writes

Sure you can! Our ETCD last implementation is currently finishing the simulation phase to open up to more customers. I can get you one in a few days to get your feedbacks ;)

Hey Justin! Here is an intent of a automated translation (I find it quite bad) youtu.be/-geAbvtPY8w?... and here is the french version youtu.be/nXj0uexEBJM?... since there has been progress you may get a better translation now :)

It actully depends on your kind of writes, if there are transactional conflicts, and keep’in mind you can change the storage engine between LSM and b+tree to accomodate with your use case

Damien Saez