KSQL-1786: First draft of KSQL and KStreams topic [WIP] #2142
Conversation
| ###################### | ||
|
|
||
| KSQL is the streaming SQL engine for Apache Kafka®. With KSQL, you can write | ||
| real-time applications by using a SQL-like query language. |
There was a problem hiding this comment.
change real-time with streaming.
There was a problem hiding this comment.
Or if you wanna keep real-time use real-time streaming.
| KSQL is the streaming SQL engine for Apache Kafka®. With KSQL, you can write | ||
| real-time applications by using a SQL-like query language. | ||
|
|
||
| Kafka Streams is the Apache Kafka® library for writing real-time applications |
|
|
||
| .. image:: ../img/ksql-kafka-streams-core-kafka-stack.png | ||
|
|
||
| KSQL gives you the highest level of abstraction for implementing real-time |
There was a problem hiding this comment.
again use real-time streaming or streaming instead of only real-time.
| that's required for real-time operations on streams of data, so that one line | ||
| of KSQL can do the work of a dozen lines of Java and Kafka Streams. | ||
|
|
||
| For example, to implement fraud-detection logic on a Kafka topic named |
There was a problem hiding this comment.
Maybe reword it so it shows that we know this is a very simple fraud detection approach!
There was a problem hiding this comment.
Also you may want to include the function for fraud probability in the query. Maybe something like this:
CREATE STREAM fraudulent_payments AS SELECT fraudProbability( data) FROM payments WHERE fraudProbability( data) > 0.8;
| } | ||
|
|
||
| KSQL is easier to use, and Kafka Streams is more flexible. Which technology | ||
| you choose for your real-time applications depends on a number of |
| | from Python, Go, C#, JavaScript, shell | | | ||
| +----------------------------------------------------+------------------------------------------------------+ | ||
|
|
||
| KSQL is usually not a good fit for BI reports and ad-hoc querying, or queries with random access patterns. |
There was a problem hiding this comment.
Maybe add the following:
KSQL is usually not a good fit for BI reports and ad-hoc querying, or queries with random access patterns since it's a continuous query system on data streams.
No description provided.