Hi Elias, OK, I think we do not need to agree on this point of view. In order to make the discussion more efficient, we need to focus a bit, let's talk about the query architecture's improvement.
Best, Vino Elias Levy <fearsome.lucid...@gmail.com> 于2019年4月30日周二 上午1:06写道： > On Fri, Apr 26, 2019 at 8:58 PM vino yang <yanghua1...@gmail.com> wrote: > > > I agree with your opinion that "*Flink jobs don't sufficiently meet these > > requirements to work as a replacement for a data store.*". Actually, I > > think it's obviously not Flink's goal. > > > > I would not be so sure. When data Artisans introduced > <https://www.ververica.com/blog/queryable-state-use-case-demo> Queryable > State in Flink, one of the use cases was explicitly removing the need for > external key-value stores. This mirrored Confluent's earlier > < > https://www.confluent.io/blog/unifying-stream-processing-and-interactive-queries-in-apache-kafka/ > > > introduction > of Interactive Queries in Kafka Streams, and they certainly saw querying of > streaming state as a possible alternative to traditional data stores. >
