[bcc: us...@kafka.apache.org, dev@kafka.apache.org] Hi everyone,
We would like to invite you to our first Stream Processing Meetup at LinkedIn on June 15 at 6pm. Please RSVP here: http://www.meetup.com/Stream-Processing-Meetup-LinkedIn/events/231454378 Going forward (at LinkedIn) we will host meetups for Kafka/Samza in this combined format. We have three great talks lined up for our June meetup: *Scalable Complex Event Processing on Samza @Uber* by Shuyi Chen <https://www.linkedin.com/in/shuyi-chen-33757915> The Marketplace data team at Uber has built a scalable complex event processing platform to solve many challenging real time data needs for various Uber products. This platform has been in production for some time and it has proven to be very flexible to solve many use cases. In this talk, we will share in detail the design and architecture of the platform, and how we employ Samza, Kafka, and Siddhi at scale. *Air Traffic Controller: Using Samza to Manage Communications with Members* by Cameron Lee <https://www.linkedin.com/in/cameron-lee-3846b840> Air Traffic Controller (ATC) is a system built on top of Samza which is responsible for managing many of the communication channels LinkedIn has with its members. Historically, LinkedIn has been known for sending too many emails to members which are not useful to them. The goal of ATC is to improve on that experience by providing some common functionality that multiple use cases can leverage, such as dynamic batching of messages, delivery time optimization, and channel selection. This discussion will include some of the functionality ATC provides, how Samza was leveraged to build ATC, and some challenges that we faced while building ATC. *Tuning Kafka for low latency guaranteed messaging* by Jiangjie (Becket) Qin <https://www.linkedin.com/in/jiangjieqin> Kafka is well known for high throughput ingestion. However, to get the best latency characteristics without compromising on throughput and durability, we need to tune Kafka. We will share our experiences to achieve the optimal combination of latency, throughput and durability for different scenarios. Thanks, Joel (for the Streams infrastructure team @ LinkedIn)
