618
If "Master/Slave" terminology in computing sounds bad now, why not change it to "Dom/Sub"?
(lemmy.dbzer0.com)
this post was submitted on 20 Aug 2024
618 points (88.6% liked)
Showerthoughts
29805 readers
779 users here now
A "Showerthought" is a simple term used to describe the thoughts that pop into your head while you're doing everyday things like taking a shower, driving, or just daydreaming. A showerthought should offer a unique perspective on an ordinary part of life.
Rules
- All posts must be showerthoughts
- The entire showerthought must be in the title
- Avoid politics
- 3.1) NEW RULE as of 5 Nov 2024, trying it out
- 3.2) Political posts often end up being circle jerks (not offering unique perspective) or enflaming (too much work for mods).
- 3.3) Try c/politicaldiscussion, volunteer as a mod here, or start your own community.
- Posts must be original/unique
- Adhere to Lemmy's Code of Conduct
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
For a distributed database there is also fragmentation/sharing though. In this case calling the nodes replicas is not accurate. I guess you would call these “shard” or “dsta” nodes.
You are right about the “slaves” not behaving, in fact they jump on the chance to become the “master” themselves once the current “master” goes down. Then there is the split-brain problem.
It's really more like a worker boss relationship, but I would hesitate to call database nodes “workers” because this one is usually used for a processing engine like Spark.
A lot of distributed databases use the concept of quorum to prevent split-brain. Does that make them a kind of democracy?
Usually quorum is maintained by using odd numbering so that when one node fails the next sequential node assumes the role allowing quorum-election breaking any ties.
It depends, there are too many different databases to say they all use that approach.
In Cassandra all nodes are equal, but specific nodes hold specific parts of data. The only concept is the coordinator node which is the node that got the query. All nodes can handle all queries. The coordinator node is different per request.