I agree with what kenn said, in most cases I would refer to the term runner as the adapter for translating user's pipeline code into a job representation and submitting it to the execution engine. Though in some cases they may still be used interchangeably such as direct runner?
On Wed, Jan 6, 2021 at 11:02 AM Kenneth Knowles <k...@apache.org> wrote: > I personally try to always distinguish two concepts: the thing doing the > computing (like Spark or Flink), and the adapter for running a Beam > pipeline (like SparkRunner or FlinkRunner). I use the term "runner" to mean > the adapter, and have been trying to use the term "engine" to refer to the > thing doing the computing. Do you think that users will use these two > interchangeably? Do you have recommendations about if these terms makes > sense to users? > > Kenn > > On Wed, Jan 6, 2021 at 10:23 AM Griselda Cuevas <g...@apache.org> wrote: > >> Hi dev@ community, Happy New Year! >> >> I'm working on updating the copy of a few website pages, and something >> that I want to solve is standardize how we refer to runners across the >> site. So far I've identified these definitions: >> >> - Back-end >> - Backend systems >> - Execution environments >> - Runtime >> - Runtime system >> - Runner >> >> Even when the majority of users will understand these concepts >> interchangeably, it's a good idea to be consistent so new users get >> familiar with how Beam works and its components. >> >> I'm going to start using the word "Runner" as I update the copy and will >> ask the team working in te UI revamp to do the same. Let me know if you >> have any questions/concerns. >> >
