Alternative to “master” and “slave” in entity relationship?

Question

Example: I have two tables in my database called classA and classB, and one table called classA_classB. The last one just defi

Answer 1

I found myself in this dilemma too. Thanks for asking the question.

I'm in a cluster, so we preferred:

• slave -> node
• master -> coordinator

That's a lot better.

EDIT: It is important to note for example that other projects have updated its policies, recently the Linux kernel documentation got update with this. Citing:

For symbol names and documentation, avoid introducing new usage of
'master / slave' (or 'slave' independent of 'master') and 'blacklist /
whitelist'.

Recommended replacements for 'master / slave' are:
    '{primary,main} / {secondary,replica,subordinate}'
    '{initiator,requester} / {target,responder}'
    '{controller,host} / {device,worker,proxy}'
    'leader / follower'
    'director / performer'

Recommended replacements for 'blacklist/whitelist' are:
    'denylist / allowlist'
    'blocklist / passlist'