3.5 patterns for safer event processing with kafka
Event processing applications occasionally fail and continue to do so. Subsystems are down, your processing code has bugs, the kafka cluster is rebalancing or is offline due to maintenance. Sounds familiar? Fear not, these problems can be mitigated with simple means. Beeing both a programmer and devops I have gathered some patterns to harden my processing applications. In this talk I will talk about 3.5 straight-forward patterns I have used successfully on projects to deal with issues related to event-processing-failures.
| Main language | English Proposal |
| Audience level | Intermediate |
| Type of presentation | Slides and code |
Programmer at kodemaker
Nils is working as programmer in Kodemaker. He has been working as a consultant for about 10 years and has experience with using kafka from several projects ranging from high-performance data-collection systems at Thomson Reuters to small-scale systems for processing online-events data at finn.no . Beeing both a programmer and devops, he has dealt with his share of kafka-failures and creating strategies to make resillient applications when kafka has its hiccups.
| Blog | https://nilsmagnus.github.io/ |
| Company | Kodemaker |
| @nils_magnus |