IN PERSON! Apache Kafka® Meetup (February 2025)

Hello everyone! Join us for an Apache Kafka® meetup on February 25th from 5:30pm, hosted by intelia in Melbourne!

The address, agenda, and speaker information can be found below. See you there!

📍Venue:
intelia
L3, 31 Queen St, Melbourne 3000

***
🗓 Agenda:

• 5:30pm: Doors open
• 5:30pm - 6:00pm: Pizza, Drinks, and Networking
• 6:00pm - 6:30pm: Derek Troy-West, CEO, Factor House
• 6:30pm - 7:00pm: Stephen Ermann, Senior Customer Success Technical Architect, Confluent
• 7:00pm - 7:30pm: Additional Q&A & Networking

***
💡 Speaker:
Derek Troy-West, CEO, Factor House

Bio:
Derek is a Co-Founder and CEO of Factor House and has a background in finance and distributed systems.
He began working with Apache Kafka, Cassandra, and Storm in 2012 and runs Melbourne Distributed, a meetup for engineers interested in distributed systems.

Talk:
Managing Schema Deletion and Schema References

Abstract:
Schema Registry and Confluent Cloud both support configuring schema that reference other schema. References are supported in each of AVRO, Protobuf, and JSONSchema formats.

In this talk we will explore how to create, update, and manage schema with references and explain how soft-deleted schema can impact your service costs and how to ensure schema are fully, permanently deleted (and the risks of doing so!)

---
💡 Speaker:
Stephen Ermann, Senior Customer Success Technical Architect, Confluent

Bio:
Stephen is a Senior Customer Success Technical Architect at Confluent where he sees his role as being the proactive side of support for his clients, where he helps them prevent issues, rather than solving them. Before that, he worked in the infrastructure and data fields for Snowflake, Red Hat, Tableau, Dell, Microsoft and at a Swiss private bank.

Talk:
How KIP-714 will make you love client-side monitoring all again!

Abstract:
Currently getting insights about how your Kafka clients are performing is rather complicated as it requires tooling that is completely different from how you manage your normal Kafka platform. So complicated that many organisation do not bother monitoring the end points.And that is a problem because the clients control so much in the Kafka world. The way the producers are configured will determine the data durability, and the way the consumers are configured will drive the platform's end-to-end performance.Working with my clients, I've noticed that many platform issues can be traced back to outdated libraries and/or misconfigurations.So starting with Kafka 3.7, released last year, we included the ability to monitor the end point metrics from the brokers, giving you an unified overview of what is happening in your platform, at the core and at the edges.

***
DISCLAIMER
BY ATTENDING THIS EVENT IN PERSON, you acknowledge that risk includes possible exposure to and illness from infectious diseases including COVID-19, and accept responsibility for this, if it occurs.
NOTE: We are unable to cater for any attendees under the age of 18.
***
If you would like to speak or host our next event please let us know! community@[confluent.io](http://confluent.io/)