"If you are using Artemis replication, your workers have nothing to lose, except their chains!" :D
On Tue, Jul 14, 2020, 14:00 Xeno Amess <xenoam...@gmail.com> wrote: > > In Artemis, slave is replicating > > the data on the master and replaces the master in case the master dies. > This situation seems actually quite suitable for "capitalist/worker" > > Jiri Daněk <jda...@redhat.com> 于2020年7月14日周二 下午7:42写道： > > > On Tue, Jul 14, 2020 at 1:02 PM Xeno Amess <xenoam...@gmail.com> wrote: > > > > > Like I said, I think "worker" can fully replace "slave" in every usage > in > > > activeMQ. > > > > > > > Nope, "worker" does not capture the idea. In Artemis, slave is > replicating > > the data on the master and replaces the master in case the master dies. > The > > "worker" terminology is more suitable for a situation when the master > > coordinates and all work is done on slaves. > > > > Looking at > > https://www.kernel.org/doc/html/latest/process/coding-style.html#naming, > > I'd suggest one of > > > > ‘{primary,main} / {secondary,replica,subordinate}’ ‘leader / follower’ > > > > I like the leader/follower, personally. I have a feeling I heard it > > somewhere in the context of database replication. > > > > Live / backup sounds good as well, except that "live" brings a bit of the > > echo of the notorious Unix cruelty and violence (killing children, > reaping > > zombies). > > -- > > Mit freundlichen Grüßen / Kind regards > > Jiri Daněk > > >
