Let's assign CAP to the cabinet of curiosities: https://brooker.co.za/blog/2024/07/25/cap-again.html

If you’re an experienced distributed systems person teaching new folks about trade-offs in your space, please don’t start with CAP. Tons of more interesting, more instructive, trade-offs.

Let's Consign CAP to the Cabinet of Curiosities - Marc's Blog

@marcbrooker when I skipped teaching about CAP explicitly and tried to focus on more interesting safety/liveness tradeoffs, I had a student complain that I hadn't covered the stuff they were asked about in interviews 😭
@marcbrooker This is really interesting blog post. On the point of relevance of CAP to systems such as IoT, monitoring devices, mobile apps etc. which are generally referred to as cyber-physical systems (CPSs), Edward Lee and colleagues have adapted & extended CAP to derive a new framework specifically for that. Quantifying C, A and latency (L), as well as developing an algebraic relationship between them to produce the CAL theorem. Their work appeared last year at ACM TECS: https://dl.acm.org/doi/10.1145/3609119
Consistency vs. Availability in Distributed Cyber-Physical Systems | ACM Transactions on Embedded Computing Systems

In distributed applications, Brewer’s CAP theorem tells us that when networks become partitioned (P), one must give up either consistency (C) or availability (A). Consistency is agreement on the values of shared variables; availability is the ability to ...

ACM Transactions on Embedded Computing Systems
@Saleh That looks super interesting, thanks for pointing it out to me.
@marcbrooker I really would love to hear your thoughts on this after you get the chance to go over it. Thanks Marc.
@marcbrooker Thanks for pointing to Bernstein & Das 2013 paper on rethinking eventual consistency. I really enjoyed reading it. Also got a note from Edward that he had not come across it and it is quite useful.