GitHub user l-7-l edited a discussion: Exploring Delayed Message Support in Iggy: Use Cases & Implementation Ideas
Iggy is absolutely fantastic, _**delayed messages is sometimes quite an useful feature.**_ In our e-commerce system, we currently rely on delayed messages for three critical workflows: 1. Order timeout closure (30-minute threshold) 2. Payment settlement initiation (N days post-fulfillment) 3. Scheduled product listing management (launches/takedowns) While Iggy's performance is excellent, native delayed message support would be a valuable feature. This capability would eliminate the need for additional components, reducing technical debt. As noted by @spetz, delayed messages serve crucial roles in certain scenarios. They proposed a potential implementation approach: >"_Create dedicated topics with background jobs that move messages to >destination topics upon schedule expiration. This could be treated as a >special topic type – either allowing direct message pulls regardless of >timing, or adding a behavioral flag."_ Open questions from the proposal: 1. How might this affect consumer access patterns for standard vs. delayed topics? We welcome architecture insights and alternative implementation approaches from the community. GitHub link: https://github.com/apache/iggy/discussions/2031 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
