<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 15 Dec 2016, at 11:18, Gustavo Fernandes <<a href="mailto:gustavo@infinispan.org" class="">gustavo@infinispan.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">On Thu, Dec 15, 2016 at 9:54 AM, Emmanuel Bernard<span class="Apple-converted-space"> </span><span dir="ltr" class=""><<a href="mailto:emmanuel@hibernate.org" target="_blank" class="">emmanuel@hibernate.org</a>></span><span class="Apple-converted-space"> </span>wrote:<br class=""><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex;">The goal is as followed: allow to collect all changes to push them to Debezium and thus Kafka.<br class=""><br class="">This need does not require to remember all changes since the beginning of time in Infinispan. Just enough to:<br class="">- let Kafka catchup assuming it is the bottleneck<br class="">- let us not lose a change in Kafka when it happened in Infinispan (coordinator, owner, replicas dying)<br class=""><br class="">The ability to read back history would then be handled by the Debezium / Kafka tail, not infinispan itself.<br class=""><br class=""></blockquote><div class=""><br class=""></div><div class="">Having an embedded Debezium connector pushing everything to Kafka sounds cool, but what impact would it bring to the other stream consumers:<br class=""><br class="">* Remote listeners, which is supported in several clients apart from Java<br class=""></div><div class="">* Continuous Queries (the same)<br class=""></div><div class="">* Spark Stream<br class=""></div><div class="">* Other eventual 3rd party stream processors: Apache Flick, Storm, etc.<br class=""><br class=""></div><div class=""> </div></div></div></div></div></blockquote><br class=""></div><div>Impact as in perf impact? Potential redesign impact? Or are you thinking of another question?</div></body></html>