Exactly-once Semantics are Possible: Here’s How Kafka Does it

This commit is contained in:
binhnguyennus 2018-01-24 01:30:06 +08:00
parent 2461a63510
commit 859f371ed2

View File

@ -84,6 +84,7 @@ Contributions are always welcome!
* [Real-time Data Pipeline with Kafka at Yelp](https://engineeringblog.yelp.com/2016/07/billions-of-messages-a-day-yelps-real-time-data-pipeline.html)
* [Audit Kafka End-to-End at Uber (count each message exactly once, audit a message across tiers)](https://eng.uber.com/chaperone/)
* [Deduplication Techniques](https://en.wikipedia.org/wiki/Data_deduplication)
* [Exactly-once Semantics are Possible: Heres How Kafka Does it](https://www.confluent.io/blog/exactly-once-semantics-are-possible-heres-how-apache-kafka-does-it/)
* [Real-time Deduping at Scale with Kafka-based Pipleline at Tapjoy](http://eng.tapjoy.com/blog-list/real-time-deduping-at-scale)
* [Delivering Billions of Messages Exactly Once: Deduping at Segment](https://segment.com/blog/exactly-once-delivery/)
* [Storage](http://highscalability.com/blog/2011/11/1/finding-the-right-data-solution-for-your-application-in-the.html)