From bdf8ce0647c5907d42fc29d41cc494e7f57b1d88 Mon Sep 17 00:00:00 2001 From: Ginger Collison Date: Fri, 4 Oct 2019 11:38:37 -0500 Subject: [PATCH] Update seq_num.md --- developer/concepts/seq_num.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/developer/concepts/seq_num.md b/developer/concepts/seq_num.md index 048d044..bc19f9f 100644 --- a/developer/concepts/seq_num.md +++ b/developer/concepts/seq_num.md @@ -3,7 +3,7 @@ A common problem for one-to-many messages is that a message can get lost or dropped due to a network failure. A simple pattern for resolving this situation is to include a sequence id with the message. Receivers can check the sequence id to see if they have missed anything. Sequence numbers combined with heartbeats in the absence of new data form a powerful and resilient pattern to detect loss. Systems that store and persist messages can also solve this problem, but sometimes are overkill for the problem at hand and usually cause additional management and operational cost. -![seq numbers](/assets/images/seqno.svg) +![](/assets/images/seqno.svg) In order to really leverage sequence ids there are a few things to keep in mind: