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
