2 ms·
It's ironic that so many of you are missing the rigour, as that is exactly the thing that "undoes" the CAP arguments. Anyway, if math is what you guys are miss
by andras_gerlits 3y ago
It's ironic that so many of you are missing the rigour, as that is exactly the thing that "undoes" the CAP arguments.
Anyway, if math is what you guys are missing, it's in this science-paper linked in the article:
https://www.researchgate.net/publication/359578461_Continuous_Integration_of_Data_Histories_into_Consistent_Namespaces https://www.researchgate.net/publication/359578461_Continuou...
This is a gentler intro to the concepts. You can also read my essay on why this setup works better than the often used semantics:
https://medium.com/p/5e397cb12e63 https://medium.com/p/5e397cb12e63
There's a specific section at the end on why CAP only applies to a very specific subset of SQL databases.
- sausagefeet 3y agoMath isn't what's missing, but Mark's post is just a bunch of metaphor and no rigor. At the very least it could go over failure modes and shows how it alleviates them but other databases fail.
- andras_gerlits 3y agoWe do you one better. We show how all information can be made redundant via determinism and how that means you can supply multiple copies of them across parallel, redundant channels. My essay talks about this in detail around the latency-mitigation section and the failure-modes part, but these are questions much closer to the actual implementation. Mark discusses the new mental model behind it, I talk about technology. https://itnext.io/how-simple-can-scale-your-sql-beat-cap-and-fulfil-the-promise-of-microservices-5e397cb12e63#7df1 https://itnext.io/how-simple-can-scale-your-sql-beat-cap-and...
- sausagefeet 3y agoThis post has no rigor. "What happens if a node dies? Well another takes its place". Ok, show me. This is hand waving.