TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Discovering Anomalies in Real-Time with Apache Flink

81 点作者 GeneticGenesis大约 8 年前

5 条评论

js8大约 8 年前
Since I maintain a pretty large ETL (batch) application for a living, I am genuinely curious about this. How do you handle failure in event-processing systems? I mean in batch, it&#x27;s simple - if there is a record (event) that causes unexpected failure (or the program fails for other reason, for example it runs out of space), we just restart the batch.<p>But in event processing, unless you can afford yourself to skip events, how do you deal with that sort of thing, especially if the processing needs to keep track of internal state between events?<p>I read about event-sourcing, which kinda is a solution to that, but add checkpoints and you have pretty much batch processing again.
评论 #13660462 未加载
评论 #13659746 未加载
评论 #13660772 未加载
评论 #13660180 未加载
评论 #13660711 未加载
hackerboos大约 8 年前
&quot;The Apache Flink project is a relative newcomer to the stream-processing space. Competing Open-Source platforms include Apache Spark, Apache Storm, and Twitter Heron.&quot;<p>Can someone explain why Apache are creating projects that compete with each other? Why not focus on one?
评论 #13660640 未加载
评论 #13660827 未加载
urlgrey大约 8 年前
I&#x27;m the author of this Mux blog post and would love to take any questions or comments, as well as suggestions for future posts. Thank you for your interest!
评论 #13662345 未加载
falsedan大约 8 年前
I&#x27;d like to see more about how they used Flink, and less about their system architecture (which give great details, up until the data is processed with Flink).
评论 #13660618 未加载
dtjon大约 8 年前
We ditched Spark Structured Streaming for Flink for a Kafka consumer, processing 3B events per day. Its been extremely stable so far, and half the cost of the spark cluster
评论 #13662789 未加载