3 ms·
Hmm... well I'm not aware of an existing term that refers specifically to either the master or slave in a master-slave scenario. And any other logical word I c
by crazygringo 7y ago
Hmm... well I'm not aware of an existing term that refers specifically to either the master or slave in a master-slave scenario.
And any other logical word I can imagine ("version", "copy", "split", "part", etc.) seems just as confusing as "partition". And at least "partition" decently suggests the general idea. The other strategy -- using a made-up word like "flimflam" -- is potentially even more confusing.
What are you suggesting instead?
- JohnBooty 7y agoI'm not sure exactly what they were doing. It doesn't sound like anything novel. (Also doesn't sound like master/slave, which typically refers to a replication setup) Sounds like they had some tables in one database and some tables in another. If they were using MySQL's built-in capabilities to do such a thing, and wanted to combine things at the database level there is already a specific term for that: federation. https://dev.mysql.com/doc/refman/5.6/en/federated-create-server.html https://dev.mysql.com/doc/refman/5.6/en/federated-create-ser... Or perhaps they took a more service-oriented approach, in which the databases don't talk directly to each other but instead expose their data via some application layer. In which case there's a term for that: a service-oriented architecture.