@U076R6N1L Thanks, good to see generic solutions for this important problem! One piece of feedback: it would have been nice for the configuration keywords to be namespaced, e.g :superlifter.triggers/queue-size etc.

hi @U4LJRA116 thank you for the feedback, could you help me understand what the benefit would be? these keys are kept within the superlifter context and so do not need to live alongside other keywords that they might clash with

@U076R6N1L code clarity, and in particular configuration traceability. This would be useful as early as the project's README, where it would be apparent immediately which keywords are interpreted by this lib, and which are specific to the business domain. What's more, in real-world scenarii, don't underestimate how far upstream of calling the superlifter these configuration keys might end up, e.g as part of Integrant configuration files.