There's also https://beam.apache.org/contribute/ptransform-style-guide/ (disclaimer: I'm the main author) which is currently under "Technical docs" but probably should be moved under "Patterns" instead.
On Mon, Sep 23, 2019 at 8:27 AM Chad Dombrova <chad...@gmail.com> wrote: > There are also these two helpful articles on Dataflow patterns which are > largely applicable to Beam in general: > > > https://www.google.com/amp/s/cloudblog.withgoogle.com/products/gcp/guide-to-common-cloud-dataflow-use-case-patterns-part-1/amp/ > > > https://www.google.com/amp/s/cloudblog.withgoogle.com/products/gcp/guide-to-common-cloud-dataflow-use-case-patterns-part-2/amp/ > > Perhaps these can be ported to the official Beam docs? > > -chad > > > On Sun, Sep 22, 2019 at 10:57 PM Reza Rokni <r...@google.com> wrote: > >> Great idea! >> >> In terms of patterns we do have a section in the docs, would be great for >> more contributors to it! >> >> https://beam.apache.org/documentation/patterns/overview/ >> >> Cheers >> >> R >> >> >> On Sun, 22 Sep 2019 at 13:43, dev wearebold <wearebold....@gmail.com> >> wrote: >> >>> Hey, >>> >>> That’s a very good idea, this could help people a lot >>> >>> >>> Regards, >>> >>> J >>> >>> > Le 22 sept. 2019 à 06:39, deepak kumar <kdq...@gmail.com> a écrit : >>> > >>> > Hi All >>> > I guess we need to put some examples in the documentation around best >>> coding practises , concurrency , non blocking IO and design patterns while >>> writing Apache Beam pipelines. >>> > Is there any such guide available ? >>> > E.g. when there are lot of options to be used in the pipeline , >>> BuilderPattern should be used. >>> > Another use case can be when anyone wants to run complex >>> transformation on incoming objects , visitor pattern should be used. >>> > This guide can come from people already running beam in production and >>> written it with all best practices in mind. >>> > It will help in greater and wider adaoption. >>> > >>> > Just a thought. >>> > Please let me know if anyone wants to contribute and i can lead this >>> initiative. >>> > >>> > Thanks >>> > Deepak >>> >>> >> >> -- >> >> This email may be confidential and privileged. If you received this >> communication by mistake, please don't forward it to anyone else, please >> erase all copies and attachments, and please let me know that it has gone >> to the wrong person. >> >> The above terms reflect a potential business arrangement, are provided >> solely as a basis for further discussion, and are not intended to be and do >> not constitute a legally binding obligation. No legally binding obligations >> will be created, implied, or inferred until an agreement in final form is >> executed in writing by all parties involved. >> >
