tlberglund

5 ms·

1.
Binge watch the "Monitoring Apache Kafka with Confluent Control Center" videos(confluent.io)
16 points by tlberglund 9y ago|0 comments
2.
by tlberglund 9y ago
Agreed that this is a newer architectural paradigm and a younger product. Of that there is no doubt, and there is always risk there. Also return, of course; someone had to deploy an RDBMs for the first time too—and everyone is glad they did
3.
by tlberglund 9y ago
Your statements about data retention are true, but if I may, I think they are only vacuously true. There are definitely ways to configure data retention incorrectly, but it seems like the folks at NYT have cracked the nut. Indeed, this is a
4.
by tlberglund 9y ago
I don't mean to be cavalier about misconfiguration, but it's not like the retention period is the Sword of Damocles. It's a configuration setting, and Kafka honors it reliably. As other commenters have pointed out, there are
5.
by tlberglund 9y ago
It may be unfair to describe setting a documented configuration parameter as "fiddling." Retention is seven days by default. It is trivial to set it to arbitrarily long periods of time. To my knowledge, this functionality isn&#x27
6.
by tlberglund 9y ago
Precisely. While "all NYT data since 1851" sounds like a lot, and >8660 days sounds like a long retention period for a Kafka topic, this--like most systems in the world--is not a Big Data application. One of the key insights fr
7.
by tlberglund 9y ago
You are not even a little bit confused! I think you have it perfectly right. And you are not alone in not thinking of Kafka as persistent storage, but when you get down to it there is no reason not to, and people are indeed using it in just
8.
I Wandered Lonely as a Cloud App(timberglund.com)
2 points by tlberglund 11y ago|0 comments
9.
The Maven(timberglund.com)
1 points by tlberglund 14y ago|0 comments