nehanarkhede

6 ms·

1.
by nehanarkhede 9y ago
Disclaimer: I'm one of the creators of Kafka and founders of Confluent The best way to get the power, throughput, latency of Kafka without the operations is to use a hosted service. The one created and supported by the Kafka team is Co
2.
by nehanarkhede 9y ago
An independent program committee makes these calls and had to pick from 166 submissions. The program committee picks talks that are insightful and technically challenging.
3.
by nehanarkhede 9y ago
Agreed. We recently had a few more members added to the team and are looking to grow it even more. Also note that KSQL is built on Kafka Streams and we have a team that works just on that as well.
4.
by nehanarkhede 9y ago
Spark SQL is different from KSQL in the following ways: - Spark SQL is not an interactive Streaming SQL interface. To do stream processing, you have to switch between writing code using Java/Scala/Python and SQL statements. KSQL,
5.
by nehanarkhede 9y ago
Yes, exactly. We plan to add support for various Kafka connectors to KSQL so you can ingest/export streams from external systems, like database, and then do stream processing all using KSQL queries. The purpose is to bring Streaming ET
6.
by nehanarkhede 9y ago
Yes KSQL is ideal for use cases similar to those that CEP was initially targeted for and more - from real-time anomaly detection, monitoring, analytics to application development and Streaming ETL. As you alluded to, the big difference is t
7.
by nehanarkhede 9y ago
Mind clarifying what you mean by changes to events? If you create a STREAM or TABLE using KSQL, it makes sure that they are kept updated with every single event that arrives on the source Kafka topics. That's what you'd expect in
8.
by nehanarkhede 9y ago
There's a pretty big difference to a point that Landoop's KCQL (Kafka Connect Query Language) and Confluent's KSQL (Streaming SQL for Apache Kafka) are two different products. - KSQL is a full-fledged Streaming SQL engine for
9.
by nehanarkhede 9y ago
I'm one of the authors of Kafka. I've outlined some differences between Flink's support for streaming SQL and KSQL in this Twitter thread - https://twitter.com/juliusvolz/status/902283513382051840
10.
by nehanarkhede 9y ago
Or that Aphyr can do his best to help us improve what's built on a strong foundation of sound design, has gone through years of thinking and review by the broader Kafka community, and has been through months of testing.
11.
by nehanarkhede 9y ago
Re: TCP, it only maintains sequencing guarantees over the lifetime of a single connection. Obviously this is too weak of a guarantee for Kafka as leaders can change in a cluster. We've built idempotence in a way that makes the sequence
12.
by nehanarkhede 10y ago
I'm one of the Kafka authors, so admittedly my view might be slightly biased Here is a quick comparison of Kafka and Pulsar: - Kafka is a complete streaming platform vs a messaging system which is what Pulsar is. Through Kafka Connect
13.
Event sourcing, CQRS, stream processing and Apache Kafka: What's the connection?(confluent.io)
15 points by nehanarkhede 10y ago|1 comments
14.
Kafka Streams and Flink: a comparison and guideline for users(confluent.io)
6 points by nehanarkhede 10y ago|0 comments
15.
Apache Kafka 0.10 is released(confluent.io)
2 points by nehanarkhede 10y ago|0 comments
16.
Hello World, Kafka Connect and Kafka Streams(confluent.io)
2 points by nehanarkhede 10y ago|0 comments
17.
Announcing Kafka Streams: Stream Processing Made Simple(confluent.io)
49 points by nehanarkhede 11y ago|3 comments
18.
Apache Kafka 0.9.0.1 is released(confluent.io)
2 points by nehanarkhede 11y ago|0 comments
19.
Announcing Kafka Connect: Building large-scale low-latency data pipelines(confluent.io)
12 points by nehanarkhede 11y ago|1 comments
20.
by nehanarkhede 11y ago
That observation is correct. Currently, people misuse stream processing systems like Storm and Samza for data import/export. This is an overkill. Kafka Connect is focused on providing scalable and operational connectors to various syst
21.
by nehanarkhede 11y ago
Your critique is well received. The Apache Kafka project has support for the Java clients and the non-java clients will be developed and available in a federated manner. At Confluent, we are focused on providing first class non-java clients
22.
by nehanarkhede 11y ago
Thanks!
23.
Apache Kafka 0.9 is released(confluent.io)
163 points by nehanarkhede 11y ago|37 comments
24.
Apache Kafka hits 1.1 trillion messages per day – Joins the 4 comma club(confluent.io)
6 points by nehanarkhede 11y ago|0 comments
25.
by nehanarkhede 11y ago
Thank you!
26.
Distributed consensus reloaded: ZooKeeper and replication in Kafka(confluent.io)
82 points by nehanarkhede 11y ago|18 comments
27.
Want Apache Kafka to Work with Apache Mesos? Here's How(confluent.io)
15 points by nehanarkhede 11y ago|1 comments
28.
Confluent Raises a Series B(confluent.io)
32 points by nehanarkhede 11y ago|4 comments
29.
Real-Time Full-Text Search with Luwak and Samza(blog.confluent.io)
85 points by nehanarkhede 11y ago|30 comments
30.
Hands-free Kafka Replication: A lesson in operational simplicity(blog.confluent.io)
36 points by nehanarkhede 11y ago|0 comments

More ›