Semi-related: one of the things that really bugs me about master/slave terms as applied to databases is that it's a really bad metaphor. Sure, one node controls

Semi-related: one of the things that really bugs me about master/slave terms as applied to databases is that it's a really bad metaphor. Sure, one node controls all of the other nodes, but if the master node dies one of the slaves will randomly get promoted to master. Or if you need to move regions maybe another slave will get promoted to master while the master will get demoted to slave. Needless to say, this isn't how most slavery systems have worked the world over. I feel that writer/reader terms are more accurately descriptive anyhow.