|
|
|
|
|
|
by EdwardDiego
1360 days ago
|
|
|
1. Kafka isn't a message queue, but advance consumer offsets past bad data. Hit person who inserted test data into prod with a cricket bat and then hit person who designed a system where they could do that with the same cricket bat, but harder. 2. Kafka - do what you did with your DB consumers. 3. Kafka - consumers going down can't cause duplicates, what's even going on with your queue? |
|
|
A message with the latest state of an object gets pushed into queue. When noone is consuming those, you essentially get duplicates: queue contains all of the updates, but you only care about the most recent one.