🎄 Happy Holidays! 🥳
Most of Solace is closed December 24–January 1 so our employees can spend time with their families. We will re-open Thursday, January 2, 2024. Please expect slower response times during this period and open a support ticket for anything needing immediate assistance.
Happy Holidays!
Please note: most of Solace is closed December 25–January 2, and will re-open Tuesday, January 3, 2023.
Resubmission of Events
I just wanted to understand how others handle the resend requirement with solace.
Following Use Cases where you need to resend some events:
Initial Load (multi instance system and new system requires some data)
=> send all data from object store to new instance (do not impact others)Resend some events for certain period of time
=> send time filtered events to one specific subscriber
Here my thoughts:
Pros:
- Re-uses the existing filters each subscriber defined to filter into the customer queue
- Clone on CI/CD which creates Queue and Subsription to clone each topic by replacing "ALL" (2nd position) with subscriber system name in this case SYS1
Cons:
- Confusing why on pub sub the target (which normally should not be known) should
be part of the topic name.
Pros:
- Direct push to subscriber queue (as resend is intended just to 1 subscriber) as no impact to others should exists
Cons:
- Loosing the subscription filters between queue and topic
Workaround: Read out the filters set and apply these topics to filter out the
matching topics from event store.
