Kafka for Architects • Ekaterina Gorshkova & Viktor Gamov • GOTO 2026
Keywords
Summary
130 words
Critical Evaluation
The interview provides valuable insights into the practical application of Apache Kafka, drawing on Ekaterina Gorshkova’s extensive experience. The discussion is grounded in real-world scenarios, such as the migration from Oracle Service Bus to Kafka Streams, which illustrates the benefits and challenges of adopting Kafka in an enterprise environment. The emphasis on data contracts and organizational architecture is particularly relevant, as these are often overlooked aspects of Kafka implementations. The speakers highlight that while Kafka’s technical capabilities are robust, the human factors—such as communication between teams and managing schema changes—are critical to success. This aligns with established best practices in event-driven architecture. The conversation also touches on the comparison with other technologies like Apache Pulsar, noting that Kafka’s community is a significant advantage. The discussion on Kafka’s role in AI systems is forward-looking, suggesting that Kafka can serve as a backbone for real-time data and agent orchestration. However, the content is primarily anecdotal and based on personal experience, lacking empirical data or case studies. The arguments are coherent and well-structured, but they are not supported by citations or references to external sources. The title accurately reflects the content, which focuses on architectural considerations for Kafka. Overall, the video offers practical knowledge for software architects and engineers, but it is not a rigorous scientific analysis. The lack of formal sources and the reliance on personal anecdotes limit its scientific value, though it remains informative for practitioners.
235 words
Title / Content Match
The title accurately reflects the content, which focuses on architectural considerations for Kafka, as discussed by the author of 'Kafka for Architects'.
Quality & Reliability
8/10
The discussion is based on the author's extensive practical experience with Kafka since 2015, including real-world projects and architectural insights. The content is coherent and aligns with established knowledge in the field, though it is primarily anecdotal and not peer-reviewed.
Chapters
Cited Sources
- GOTO Book Club — The interview was recorded for the GOTO Book Club series.
- Ekaterina Gorshkova on LinkedIn — Profile of the author and guest.
- Ekaterina Gorshkova on Medium — Articles and publications by the author.
- Viktor Gamov on Bluesky — Profile of the host.
- Viktor Gamov on X — Profile of the host.
- Viktor Gamov on GitHub — Code repositories and projects.
- Viktor Gamov on LinkedIn — Profile of the host.
- Viktor Gamov's website — Personal website with resources.
- GOTO Episode 440 — Episode page for this interview.
- Current Confluent London — Event mentioned in the description.
Concurring Sources
- Kafka in Action — Co-authored by Viktor Gamov, this book covers Kafka fundamentals and is referenced in the discussion.
- Kafka for Architects — Ekaterina Gorshkova's book, which is the main topic of the interview.
External References
Contribution & Novelties
The video provides a practitioner’s perspective on Kafka architecture, emphasizing the importance of organizational aspects and data contracts. It offers insights into the transition from traditional integration platforms to Kafka Streams and discusses the role of Kafka in AI-driven systems. The discussion highlights the value of community support and the challenges of adopting Kafka in enterprises.
Pour aller plus loin :
- Apache Kafka Documentation — Official documentation for Kafka concepts and configuration.
- Event-Driven Architecture — Martin Fowler’s article on event-driven architecture patterns.
- Kafka Streams — Official documentation for Kafka Streams library.
- Schema Registry — Confluent’s documentation on schema management for Kafka.
101 words
Radar Profile
The radar profile shows high scores in quality of information and reliability, reflecting the expert experience shared. The quantity of information is moderate, and the technical level is high, indicating a focused discussion for an audience with some Kafka knowledge.