You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instead of relying on lifecycle policies that will remove the parcels after 6 months (the maximum TTL), we should have a background mechanism that automatically deletes expired parcels. This only applies to parcels whose delivery (if any) hasn't been acknowledged by the recipient, since we still delete parcels upon receiving their ACK.
NATS Streaming doesn't support delayed messages so we'll have to use a different backing service. For example, we could index parcels in MongoDB and run a query periodically to filter expired parcels.
The text was updated successfully, but these errors were encountered:
Instead of relying on lifecycle policies that will remove the parcels after 6 months (the maximum TTL), we should have a background mechanism that automatically deletes expired parcels. This only applies to parcels whose delivery (if any) hasn't been acknowledged by the recipient, since we still delete parcels upon receiving their ACK.
NATS Streaming doesn't support delayed messages so we'll have to use a different backing service. For example, we could index parcels in MongoDB and run a query periodically to filter expired parcels.
The text was updated successfully, but these errors were encountered: