title: Redis Redisson - Strategies for workers
body: <p>I am new to redis, and redisson but kind of up to date with what is available now.</p>
  <p>Mostly from here: <a href="https://github.com/redisson/redisson/wiki/9.-distributed-services#91-remote-service" rel="nofollow noreferrer">https://github.com/redisson/redisson/wiki/9.-distributed-services#91-remote-service</a></p>
  <p>The case here involves a <strong>worker</strong>, on only one server out of say many. The worker gets to images which can be downloaded later on. They can be pushed to an executor to download later, however, that is not persistable and so we will loose out.</p>
  <p>Redis offers <strong>executorservice</strong>. But I was wondering, does all redis nodes share or ship in to peform the work by default? Is there a way to control that only one gets to do the work? The stuff in the runnable / callable that is being accessed, I am guessing there has to be restrictions on what could be used since it is a closure with access to environment? No access?</p>
  <p>Redis also offers something called <strong>distributed remote services</strong>. How are they different from an executorservice in this regard?</p>
  <p>Another option is to push these to reddis list / <strong>queue</strong> / <strong>dequeu</strong>, and work of the &quot;<strong>messages</strong>&quot; albeit the executor service I think would allow me to have all that logic in the same place.</p>
  <p><strong>What is the best approach?</strong></p>
  <p>What are the rules for objects inside the closure supplied in a runnable / callable ? Fully serialiazeble everything ?</p>
  <p>How do I manage if a worker is working, and suddenly dies (nuclear). Can I ensure that someone else gets <strong>to work</strong>?</p>