durable-queue does a great job already of recovering from application restart. however, it cannot handle longer-term disaster recovery very well for a couple of reasons:
- empty slabs (i.e. slabs with all
:completed tasks) get removed fairly frequently; and
- on startup, slab tasks in the
:complete state are skipped over even if you provide a :complete? fn
as it stands now, when using durable-queue a secondary storage solution is necessary to be able to replay events in the case that downstream repairs are required.
it would be nice if durable-queue could handle being able to archive/replay slabs at the user's discretion.
durable-queuedoes a great job already of recovering from application restart. however, it cannot handle longer-term disaster recovery very well for a couple of reasons::completed tasks) get removed fairly frequently; and:completestate are skipped over even if you provide a:complete?fnas it stands now, when using
durable-queuea secondary storage solution is necessary to be able to replay events in the case that downstream repairs are required.it would be nice if
durable-queuecould handle being able to archive/replay slabs at the user's discretion.