Because the server remembers which messages were acknowledged, a durable consumer resumes exactly where it stopped. Several instances can share the same durable name to split the work, which is how consumers scale horizontally.