HTTP REST seems like an "out of external dependency" way to go.

Personally, I like having Redis as a dependency as most of my current applications use two Redis instances; persistent store and volatile.

So ActionCable needs Redis! Is this the first time Rails is aligning with a vendor product? Why not abstract it like AR/AJ?

def handle_exception(self, job, *exc_info):

worker = Worker(..., exception_handler=[handle_exception])
try:
    raise Exception()
except Exception:
    exc_info = sys.exc_info()

worker.handle_exception(job, *exc_info)

failure_ttl

result_ttl=600

job.meta['handled_by'] = socket.gethostname() job.save_meta()

w = Worker([q], exception_handlers=[foo_handler, bar_handler])

def my_handler(job, exc_type, exc_value, traceback): # do custom things here

But the reason is that, if your host system does not have the vm.overcommit_memory=1 enabled, you will not be able to switch it inside container.

This in turn means that Redis Cluster does not have to take meta data in the data structures in order to attempt a value merge, and that the fancy commands and data structures supported by Redis are also supported by Redis Cluster. So no additional memory overhead, no API limits, no limits in the amount of elements a value can contain, but less safety during partitions.