[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (OSLCCORE-93) Enforce consecutive order of the trs:order numbers
Andrii Berezovskyi created OSLCCORE-93: ------------------------------------------ Summary: Enforce consecutive order of the trs:order numbers Key: OSLCCORE-93 URL: https://issues.oasis-open.org/browse/OSLCCORE-93 Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC Issue Type: Bug Reporter: Andrii Berezovskyi If TRS events are to be distributed via messaging systems without strict ordering guarantees (eg partitioned Kafka topics), a Resequencer EIP pattern might need to be applied. The pattern requires the message order ids to be sequential in order to unambiguously define whether there are any out-of-order messages still missing from the internal resequencing buffer. I think a single atomic counter is not too much to ask from the TRS server implementers. http://www.enterpriseintegrationpatterns.com/patterns/messaging/Resequencer.html -- This message was sent by Atlassian JIRA (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]