andras_gerlits

7 ms·

1.
Staying on Top in the Age of LLMs(andrasgerlits.medium.com)
2 points by andras_gerlits 8mo ago|0 comments
2.
Clearing Is a Distributed System Problem and That's Bad News for Stablecoins(andrasgerlits.medium.com)
3 points by andras_gerlits 1y ago|0 comments
3.
by andras_gerlits 1y ago
(...) What this means is that we lose many efficiencies when we talk about configuration as different from data. The fact is, no matter how much we’re trying to separate the two, configuration is data. All major outages experienced by (gene
4.
by andras_gerlits 2y ago
"I stand by spreading hearsay, even if a court happens to disagree"
5.
by andras_gerlits 3y ago
I can only repeat what I told you earlier. Our distributed consistency model meets the SQL-standard's requirements for consistency and tolerates such outages. This is a fact. CAP is a bad model for more reasons than the ones listed in
6.
by andras_gerlits 3y ago
CAP means many different things. If you took the time to read what I have to say about it, you would know that I'm saying that we're beating the requirements Brewer sets out in his original presentation, where he introduces the co
7.
by andras_gerlits 3y ago
There's a mental leap you need to make before it clicks into place and I can't do it for you. I have several people who understand what I say and why I say it, but I get that this isn't an easy step to make. If you read the e
8.
by andras_gerlits 3y ago
The reason you don't understand why my claims are different from being just another solution with clocks and mutexes is because you haven't actually engaged with the essence of it. I'll give you a hint: the consistency mechan
9.
by andras_gerlits 3y ago
We need to clarify first if we're talking about CAP or real life. CAP requirements are absurd. To quote Dominick Tornow from here: https://blog.dtornow.com/the-cap-theorem.-the-bad-the-bad-th... "Note that Gilbert
10.
by andras_gerlits 3y ago
Okay, so we can move beyond CAP. So we don't talk about implementation in either the science-paper or in the intro for it (which is what this thread is about). I mostly write about implementation, Mark mostly writes about the science.
11.
by andras_gerlits 3y ago
Well no, by making the probability of latency-events extremely unlikely by establishing redundant channels. https://medium.com/p/5e397cb12e63#7df1 Considering that this is maybe the 12th time I'm linking the expla
12.
by andras_gerlits 3y ago
It's clear for everyone that if you define Consistency via Linearizability, CAP-like problems will apply, as you're necessarily creating original information on a potentially remote node. That's not the issue. The issue is th
13.
by andras_gerlits 3y ago
Yes, that's exactly the problem with the existing models and why CAP was formalised.
14.
by andras_gerlits 3y ago
Can I replicate people deterministically and control all their sensory inputs in this scenario?
15.
by andras_gerlits 3y ago
No. CAP requires linearizability for its definition. If your consistency-model moves with the network's ability to communicate, your strong consistency can progress even if you somehow manage to lose your redundant replicas. This is wh
16.
by andras_gerlits 3y ago
Any modification to existing data must be "haggled for" somewhere, you're right about that. When you say "partition event", what is being partitioned here? A specific communication-link between two nodes. It's
17.
by andras_gerlits 3y ago
It's fine to not understand things. Being condescending is a natural reaction to feeling challenged, I really do understand where you're coming from. It's not even your fault, really. Anyway, when you're ready, feel free
18.
by andras_gerlits 3y ago
Almost there Dustin, thank you. This article is about the mental model behind scaling consistency across arbitrary geographical distances and how this model allows us to communicate time-information the same way we now communicate data. It&
19.
by andras_gerlits 3y ago
This section discusses some failure modes (the first one is about the failure of a specific node): https://itnext.io/how-simple-can-scale-your-sql-beat-cap-and... This section discusses latency-spike mitigation (which is ho
20.
by andras_gerlits 3y ago
Sure, there are other ways of doing this, the demos don't prove what I say, they only show that the theory works on a practical level. The science-paper however, does show how this mechanism can scale consistency. Think about it this w
21.
by andras_gerlits 3y ago
Sure. Here: https://medium.com/p/5e397cb12e63#04a5
22.
by andras_gerlits 3y ago
We 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-mi
23.
by andras_gerlits 3y ago
PACELC is an extension of CAP, so it suffers from the same problem of trying to apply a universal clock to the whole system. If you do that, you will suffer these limitations. With client-centric consistency, you can work around these probl
24.
by andras_gerlits 3y ago
I don't think I ever heard people accuse our paper of not being rigorous enough, but more than happy to listen to specific problems with it: https://www.researchgate.net/publication/359578461_Continuou...
25.
by andras_gerlits 3y ago
The CAP argument falls apart as soon as you decouple consistency from wall-clocks. Consistent systems only suffer from CAP limitations if they need strict serializability. The point is that if you only look at the order of the data and not
26.
by andras_gerlits 3y ago
I also have a demo here where I show transactionality between two SQL-databases, a MySQL and a Postgres instance: https://www.youtube.com/watch?v=XJSSjY4szZE And another, where I show loose coupling, ie: that the system con
27.
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
28.
Using Promise Theory to solve the distributed consensus problem(mark-burgess-oslo-mb.medium.com)
51 points by andras_gerlits 3y ago|55 comments
29.
by andras_gerlits 3y ago
How to decentralise and scale distributed consistency beyond the commonly accepted limits
30.
by andras_gerlits 3y ago
How we built the world's first loosely coupled, ACID, master-master platform that can accommodate any mainstream SQL-database.

More ›