Mailing-List: contact dev-help@flink.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flink.apache.org
MIME-Version: 1.0
From: Stavros Kontopoulos <st.kontopoulos@gmail.com>
Date: Fri, 30 Jun 2017 11:58:24 +0300
Message-ID: <CACTd3c87e0c-KjoQ1exd7772SdR3SqamL0s5uAHTrP+YTFRMCA@mail.gmail.com>
Subject: [DISCUSS] FLIP proposal for Model Serving over Flink
To: dev@flink.apache.org, Boris Lublinsky <boris.lublinsky@lightbend.com>,
	Eron Wright <ewright@live.com>, Roberto Bentivoglio <roberto.bentivoglio@radicalbit.io>,
	Riccardo Diomedi <riccardo.diomedi@radicalbit.io>,
	Mauro Cortellazzi <mauro.cortellazzi@radicalbit.io>,
	"Geerdink, A.S. (Bas)" <Bas.Geerdink@ing.nl>, Andrea Spina <andrea.spina@radicalbit.io>
Content-Type: multipart/alternative; boundary="94eb2c1915e0b7c68c0553299ed0"
archived-at: Fri, 30 Jun 2017 08:58:30 -0000

--94eb2c1915e0b7c68c0553299ed0
Content-Type: text/plain; charset="UTF-8"

Hi all,

After coordinating with Theodore Vasiloudis and the guys behind the Flink
Model Serving effort (Eron, Radicalbit people, Boris, Bas (ING)), we
propose to start working on the model serving over Flink in a more official
way.
That translates to capturing design details in a FLIP document.

Please let's discuss and vote whether you think this FLIP would be viable.

Model Serving as a Flink component might involve a lot of work and we need
to commit to support it in future Flink releases.

In the mean time a lot of people have joined Flink ml slack channel (
https://flinkml.slack.com, https://flinkml-invites.herokuapp.com/) and I
think its time to try get them gradually on board.

So far we have several efforts hosted here: https://github.com/FlinkML

Related documents for what we are doing:

Flink ML roadmap

https://docs.google.com/document/d/1afQbvZBTV15qF3vobVWUjxQc49h3U
d06MIRhahtJ6dw/edit

Flink MS

https://docs.google.com/document/d/1CjWL9aLxPrKytKxUF5c3ohs0ickp0
fdEXPsPYPEywsE/edit#

PS. I will work on the last document the next few days to consolidate
effort results to some extend and break work down.
Our target is to provide a generic API based on some plugin architecture to
serve different popular models/pipelines along with custom ones over flink.

Best,
Stavros

--94eb2c1915e0b7c68c0553299ed0--