Kafka at PagerDuty and Schema Registry by Confluent

Join us for our next Apache Kafka® meetup on August 15th from 6:00pm at PagerDuty in San Francisco. The address, agenda and speaker information can be found below. See you there!

-----

Agenda:

6:00pm: Doors open
6:00pm - 6:30pm: Pizza, Drinks and Networking
6:30pm - 7:00pm: Peter Kennedy, PagerDuty
7:00pm - 7:30pm: Magesh Nandakumar, Confluent
7:30pm - 7:45pm - Additional Q&A & Networking

------

Speaker:
Peter Kennedy

Bio:
Canadian Software engineer at PagerDuty out of San Francisco focusing in distributed systems, chaos engineering, and that wonderful intersection between. Peter has been active in the devops community in the Toronto and San Francisco area for a short while; when not coding or causing major incidents he is hiking tall mountains and travelling to faraway countries.

Title:
Keeping the lights on by burning down everything.

Abstract:
My company is responsible for waking up our customers when their systems fail. If our services fail our customers won’t receive their pages. Detecting these failures early is important, but our success in reliability has come from our engineers routinely breaking our product on purpose to find problems before our customers.

Chaos Engineering is well established at my organization. Over six years of purposely breaking our own systems have lead to a much more reliable product for our customers. This practice has also lead to a strong culture of continually breaking our own product in production so that our users don’t have to.

Kafka, however, has been comparably much more recent. All of our transient data relies on Kafka for our product to function, but how does Kafka behave on the extreme end of failure. What kinds of stress can we put Kafka and still function as we need. From shutting down a consumer to simulating a full datacenter loss, this talk will explore what we learned from taking Kafka to its limits and what it took to fully break Kafka. This talk will also explore our culture of Chaos Engineering at my company, how we regularly break Kafka in production, as well as tips and tricks to get started with Chaos engineering with Kafka.

--------

Speaker:
Magesh Nandakumar

Bio:
Magesh Nandakumar is a Software Engineer at Confluent working on Kafka Connect and Schema Registry. Prior to Confluent, he worked at various Fin Tech companies. During his tenure at Visa, he started using Kafka for Fraud detection and ever since has been fascinated about it. During his spare time, he loves to to plays cricket and loves to spend his time with his Son and Daughter

Title:
Schema - The data contract for event processing

Abstract:
In a world of event/stream processing that communicate via unbounded streams of events, schemas are the contracts between the services/applications. Having an agreed contract allows the teams developing those services to move fast, by reducing the risk involved in making changes. This allows decoupling between the applications. Additionally, this also enables decoupling between the teams allowing them to operate independently. Yet delivering events with schema change in mind isn’t the common practice yet.
In this presentation, we’ll discuss patterns of schema design, schema storage and schema evolution that help development teams build better contracts through better collaboration - and deliver resilient applications faster. We’ll look at how Confluent Schema Registry can be used in the context of Kafka Clients, Kafka Connect, Stream Processing & KSQL to help achieve this contract. We will also look at some of the best practices of Schema evolution and the mapping between topics to subjects.

--------

Don't forget to join our Community Slack Team (https://launchpass.com/confluentcommunity) !

If you would like to speak or host our next event please let us know! community@confluent.io

NOTE: We are unable to cater for any attendees under the age of 18. Please do not sign up for this event if you are under 18.