The standard approach, which Kafka also uses beneath all the libraries hiding it from you, is:

The publisher has a set of tables (topics and partitions) of events, ordered and with each event having an assigned event sequence number.

Publisher stores no state for consumers in any way.

Instead, each consumer keeps a cursor (a variable holding an event sequence number) indicating how far it has read for each event log table it is reading.

Consumer can then advance (or rewind) its own cursor in whatever way it wishes. The publisher is oblivious to any consumer side state.

This is the fundamental piece of how event log publishing works (as opposed to queues which is something else entirely; and the article talks about both usecases).