As Jonas said, for job upgrades having a single job that "multiplexes" multiple jobs means that all jobs will be offline at the same time. If all jobs share a single Flink cluster, it should be fine to use multiple jobs that share the resources. A down side of this will be that managing multiple jobs is probably harder than managing just a single job (keeping track of the state, monitoring, etc.)
On Sun, Feb 5, 2017 at 10:43 PM, Jonas <jo...@huntun.de> wrote: > I recommend multiple Jobs. You can still share most of the code by creating > Java / Scala packages. THis makes it easier to update Jobs. > > > > -- > View this message in context: > http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Many-streaming-jobs-vs-one-tp11449p11450.html > Sent from the Apache Flink User Mailing List archive. mailing list archive at > Nabble.com.
