[nrser]

I clicked through to the technical intro, and it says you’re using AntidoteDB for the top-level replication

https://electric-sql.com/docs/overview/technical-intro

I happen across AntidoteDB just the other day, and my take-away was that it was still under development but not really ready for production use. Curious your opinion / experience with it?

[thruflo]

Yup, it’s a very rigorous system developed over ~10 years with solid testing, benchmarking and formal proofs. However it has some known issues, such as behaviour under high load and not currently handling node failure within a DC.

It’s not production ready and neither are we (we’re in developer preview mode, which is like a public alpha [0]).

There are also other aspects on the Antidote roadmap such as efficiently materialising consistent secondary indexes that are ongoing challenges but aren’t so relevant to how we’re using it as a replication layer.

We are working, alongside others, with the Antidote developers to help fix these issues and generally improve reliability / engineer correct behaviour under load. (Professor Annette Bieniusa, who leads the development, is our Chief Architect). We have a fork at electric-sql/vaxine [1].

We are also taking advantage of some simplifications which mitigate the known issues. We have an #antidote channel in the ElectricSQL discord [2] if you’d be interested in chatting more.

[0]: https://electric-sql.com/docs/overview/faqs

[1]: https://github.com/electric-sql/vaxine

[2]: https://discord.gg/B7kHGwDcbj

[techdragon]

I’m just going to put the idea here… C# and Blazor, with linq to sql, in the browser… automatically synced to the backend server… that just sounds like magic, but magic I would throw money at.