For this kind of decisions, I'd write a short doc with pros and cons and suggest an option. We can further discuss in the doc or dev list if needed. If there's a significant disagreement we could even go for a vote in the dev list but usually we do not get to that (and go by lazy consensus [1]).
BTW we had a very similar discussion previously regarding using one of these systems for hosting datastores for Beam I/O testing. https://lists.apache.org/thread/r0gn5fzp6zy6c277r1sqvb4o9rc45rxf Thanks, Cham [1] https://community.apache.org/committers/lazyConsensus.html On Mon, Dec 12, 2022 at 11:16 AM Damon Douglas via dev <dev@beam.apache.org> wrote: > Hello Everyone, > > *Even if this is your first day learning Beam, please feel welcome to > vote.* > > *Please cast your single question answer on your preference* for > Kubernetes [1] versus Docker Compose [2] in local development of the Beam > Playground [3]. The form provides short and long > versioned explanations, if needed. > > *https://forms.gle/GBZZ9nCzj5EvXVgQ8 > <https://forms.gle/GBZZ9nCzj5EvXVgQ8> * > > Thank you for your time and help. > > Best, > > Damon > > *References*: > > 1. Kubernetes - an open-source system for automating deployment, scaling, > and management of containerized applications. > See https://kubernetes.io/ > 2. Docker Compose - a tool for defining and running multi-container Docker > applications. > See https://docs.docker.com/compose/ > 3. Beam Playground - a full stack web application to execute Apache Beam > snippets in a modern browser. > See https://play.beam.apache.org/ >
