If any can be dropped than clearly all are not needed. What is needed differs greatly if you have a billion events versus 10. Without more information on the system you cannot create an appropriate design.
It is my guess that a simple hand off queue will suffice in this case. (Otherwise you need to worry about ring size, per element processing time, event rate, etc). > On Nov 15, 2020, at 9:33 PM, Kurtis Rader <kra...@skepticism.us> wrote: > > >> On Sun, Nov 15, 2020 at 7:21 PM Robert Engels <reng...@ix.netcom.com> wrote: > >> I will argue if it is ok to drop the oldest then it is ok to drop all but >> the latest. You need more metrics on volume and latency requirements to know >> which is the proper approach. > > If true your solution implies the O.P.'s question is an example of the XY > problem. But since the behavior they asked for was not an obvious example of > the XY problem it is reasonable to take their requirements at face value. In > my four decades of programming I've seen (or read about) many scenarios I > might have initially responded to, incorrectly, with a "WTF?". > > -- > Kurtis Rader > Caretaker of the exceptional canines Junior and Hank -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/37D6AD46-1CCE-40CF-821A-11F68AD65B9D%40ix.netcom.com.
