Abstract: A solution is provided to ensure that messages in a message broker are handled by one and only one version of a microservice application despite there being multiple versions of the microservice application running in parallel. More particularly, one version of the microservice application is designated as the leader while the others are designated as followers. When a follower has a tenant that is then promoted to be handled by the leader via a tenant assignment change, a specialized process is started by the leader that determines the current offset with the offset where the follower stopped handling messages for that tenant. If the current offset is greater, then a specialized rewind operation is performed to process any unprocessed events from the gap. If the current offset is less or equal, then a specialized fast-forward operation is performed to discard the messages addressed to the promoted tenants on the follower.

Abstract: A solution is provided to ensure that messages in a message broker are handled by one and only one version of a microservice application despite there being multiple versions of the microservice application running in parallel. More particularly, one version of the microservice application is designated as the leader while the others are designated as followers. When a follower has a tenant that is then promoted to be handled by the leader via a tenant assignment change, a specialized process is started by the leader that determines the current offset with the offset where the follower stopped handling messages for that tenant. If the current offset is greater, then a specialized rewind operation is performed to process any unprocessed events from the gap. If the current offset is less or equal, then a specialized fast-forward operation is performed to discard the messages addressed to the promoted tenants on the follower.