Make sure no messages can get lost or double-processed

[lbilger]

Scenario

• Library version:
• Description of your use case: (detailed description or executable reproducer, e.g. GitHub repo)

There might be some situations where a message can get lost (e.g. when it can't be written to the database) or be double-processed (e.g. when the ShedLock times out). We should make sure all those situations are addressed somehow.

So far, this is a placeholder to investigate if and where these issues can hit us.

Current Behaviour

Wanted Behaviour

Possible Workarounds

[lbilger]

As discussed with @zambrovski, this is probably a documentation issue only. We should add some hints to the documentation on how to configure the Kafka client and ShedLock properly to avoid such issues. The library itself has no share in these.

[zambrovski]

@lbilger do you think you can create a draft of this documentation?