miguno

5 ms·

31.
by miguno 9y ago
Small and friendly correction: Kafka bills itself as "a distributed streaming platform". Also, a heads up: we'll soon publish a blog post on the subject of "is it ok to (permanently) store data in Apache Kafka".
32.
by miguno 9y ago
> No offense, but this just shows your ignorance of the functionality that you're leaving on the table by considering SQL a cough-legacy-cough solution. No reason to get ad-hominem. When I said cough-legacy-cough, I was referring to
33.
by miguno 9y ago
Kafka can perfectly keep your data around forever. The only limitation is available disk space (and databases have the same limitation). I'm not implying that it is always the best idea to use Kafka as a long-term storage solution, b
34.
by miguno 9y ago
> I think they want to it to be durable in the sense that even if the events are already consumed they can still play them back to reindex elastic search (which is a thing you need to do periodically). That (replaying if needed) is exact
35.
by miguno 9y ago
To add to what nehanarkhede said: I'd rather see it as a testament to the powerful building blocks of Kafka and its Streams API that you can actually implement a project such as KSQL with very few engineers. Also, the commits in KSQL r
36.
by miguno 11y ago
Disclaimer: I work for Confluent (www.confluent.io). That said, let me clarify that Kafka Streams is a component of the Apache Kafka open source project. There's nothing proprietary about it. The reason the links below point to docs