Far from a controversial choice, Kafka is now a technology developers and architects are adopting with enthusiasm. And it’s often not just a good choice, but a technology enabling meaningful improvements in complex, evolvable systems that need to respond to the world in real time. But surely it's possible to do wrong! In this talk, we'll look at common mistakes in event-driven systems built on top of Kafka:
- Deploying Kafka when an event-driven architecture is not the best choice.
- Ignoring schema management. Events are the APIs of event-driven systems!
- Writing bespoke consumers when stream processing is a better fit.
- Using stream processing when you really need a database.
- Trivializing the task of elastic scaling in all parts of the system.
It's highly likely for medium- and large-scale systems that an event-first perspective is the most helpful one to take, but it's early days, and it's still possible to get this wrong. Come to this talk for a survey of mistakes not to make.
プレゼンター
Tim Berglund
Tim Berglund は、StarTree の開発者広報部門のリーダーとして、さらには教師や作家としても活躍しています。米国や世界中のさまざまな会議で頻繁に講演者を務め、O'Reilly トレーニングビデオの共同プレゼンターとして Git から分散型システムまで多彩なテーマをカバーするほか、『Gradle Beyond the Basics』の著者でもあります。ツイート (@tlberglund) やブログ投稿 (http://timberglund.com) に加え、ポッドキャスト (http://devrelrad.io) の共同ホストとしても発信しており、米国コロラド州リトルトンに長年連れ添った妻と末子と共に暮らしています(他の2人の子供はほぼ成人に近い年齢)。