지금 Current 2022: The Next Generation of Kafka Summit에 등록해서 데이터 스트리밍의 미래를 라이브로 확인해 보세요!
Do you make New Year’s resolutions? The most I personally hear about them is people making a big show about how they don’t do them. And sure enough, I don’t either, but maybe you do. For example, maybe you made a New Year’s resolution to learn Apache Kafka® better. As resolutions go, that would be a good one. I would encourage that kind resolution.
And if you did…how’s that resolution going? Do you need some help? Well, you’re in luck, because I have just the thing for you: Kafka Summit London. It’s coming up on April 27th and 28th, and we are just now ready to announce the agenda.
In the past, we’ve organized content into themed tracks, like Use Cases, Stream Processing, Event-Driven Development, and Core Kafka. I realized this actually gets in our way of selecting all the best and only the best submissions, since the interests of the community are not evenly allocated along whatever track boundaries we want to impose in any given year. We still have 56 sessions spread over four tracks, but the tracks just have numbers, not themes. This let us pick the highest-rated talks across the whole program without trying to find a certain number of use cases, or even-driven development talks, or the like.
And we didn’t make this change in a vacuum! Here is the Highly Scientific Twitter Poll I took to validate this approach:
A question for you, friends. When you’re attending a technology conference, do defined track themes help you think about content, or do you just look at what’s happening in a slot and pick something? RT this if you don’t terribly mind…
— Tim Berglund (@tlberglund) January 14, 2020
Confidential to the 22.2% of you who like tracks: we have tags. Each speaker has had the opportunity to add appropriate tags to their talk, so you’ll have an easy way of seeing what subjects each session intends to cover. (Not that reading the abstract was all that hard, but hey, tags often make more sense than categories anyway.)
Given this change, maybe you’re wondering where to start and how you can go about picking the right talks for you. Might I suggest some as a start? Here are a few that I’m especially looking forward to and highly recommend checking out:
We’ve also got two keynotes to offer: one from Jay Kreps and another from Sam Newman. Each of these leaders has been influential in shaping the worlds of Apache Kafka and distributed systems today, and we are excited to be hearing from them about what they’re thinking and what they think is next. It’s a bit early for me to tell you too much about what’s in those keynotes, but if you know these two speakers, you know enough to know you want to hear them.
It is my privilege to work alongside the Kafka Summit Program Committee, many of whom have joined this year and have spent hours reviewing and rating abstracts. I’d like to thank them for all their hard work in curating a fine agenda and for making this exciting event possible. By name, they are:
Register for Kafka Summit London today with the code KSL20Blog to get 30% off.
If you can’t make it to London, there is another chance to attend or present at a summit later this year. The Kafka Summit Austin call for papers is now open, and we encourage you to submit a talk. For help with crafting something, feel free to share your idea in the #summit-office-hours channel on the Confluent Community Slack to get feedback. And more importantly, if you want tips on how to write a winning abstract, please watch the video below for some tips on how to make your submission stand out:
We’d love to hear from you!
Tim Berglund is a teacher, author and technology leader with Confluent, where he serves as the senior director of developer relations. He can frequently be found at speaking at conferences in the U.S. and all over the world. He is the co-presenter of various O’Reilly training videos on topics ranging from Git to distributed systems, and is the author of Gradle Beyond the Basics. He tweets as @tlberglund and lives in Littleton, CO, U.S., with the wife of his youth and their youngest child, the other two having mostly grown up.