[
https://issues.apache.org/jira/browse/FLINK-6085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chen Qin updated FLINK-6085:
----------------------------
Attachment: Untitled document.jpg
I would like to see if we can agree on high level first. Service is primarily
rpc interaction with horizontal scalability and latency requirements.
Current way of bridge service with streaming pipeline via distributed Queue
provides benefit of failure resilience and topic reuse at cost of extra
hardware/software and latency, also no callback support.
[~till.rohrmann]
> flink as micro service
> ----------------------
>
> Key: FLINK-6085
> URL: https://issues.apache.org/jira/browse/FLINK-6085
> Project: Flink
> Issue Type: Improvement
> Components: DataStream API, JobManager
> Reporter: Chen Qin
> Priority: Minor
> Attachments: Untitled document.jpg
>
>
> Track discussion around run flink as a micro service, includes but not
> limited to
> - RPC (web service endpoint) source
> as web service endpoint accept RPC call, ingest to the streaming job(only
> one)
> - callback mechanism
> - task assignment should honor deployment group (web tier hosts should be
> isolated from rest of task assignment)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
