Time for a new speaker interview again. I spoke to Katrin Shechtman to find out how Microservices and Checklists go together.
Katrin is a Software Engineer with years of experience developing large platforms in C, C++, Java and Scala utilizing many different frameworks. She currently works at Lightbend as Enterprise Architect helping big enterprises embrace a world of Reactive Systems and Big Data.
Markus E: “Thank you so much for taking the time out of your packed days to have this little interview with me. Everybody is a first time speaker at this years Reactive Summit.
What are your personal expectations?”
Katrin: “For speakers I’m expecting to be among like minded programmers and architects who are obsessvily Reactive. If it doesn’t say much to you, then this conference just got more interesting. For audience, I’m expecting a bunch of passionate folks that will question everything said or showed on stage. Great audience never takes anything for granted and I’m sure that this time it will be even more so.”
ME: “You’re combining a hype topic like Microservices with checklists.
While everybody is still experimenting with Microservices, how can you
already talk about checklists? What is technical backround?”
K: “During last two years I’ve intensively worked on several different a large scale projects with both startups and enterprise clients. Some of these projects were green field, while some others aimed to modernize aging systems. When you work on so many different systems in such a short period of time, at some point you inevitably start recognizing patterns in reasons why some of them are smoother than the others. This talk summarized these patterns of what might go wrong and how it can be prevented.”
ME: “What is your background as programmer? What was the most difficult
thing to learn when starting to work with Reactive Applications.”
K: “My background is rather ‘hectic’. Though my Master degree is in Distributed Systems, my first industry job focused on developing kernel mode Windows drivers in C followed by number of adventures including several J2EE apps, distributed computing software in C++, couple of Play! and Akka projects and ultimately working as consultant and trainer at BoldRadius and as Enterprise Architect at Lightbend. The toughest thing I had let go when I started building Reactive systems was the convenience of a “system won’t crash” approach. I didn’t realize how cozy it was till I’ve realized systems not only can, they will definitely crash, the question is what I as developer can do to make sure that when it happens, it doesn’t cause havoc but rather gets automatically back to normal as quickly as possible. ”
ME: “If you look at the Reactive Summit schedule, what is the one talk
you look forward to the most and why?”
K: “I’m looking forward to ‘The Demo Gods are (not) on our side!’ talk by Christopher Hunt. Knowing Christopher and his team members personally and following the impressive work they have done in Reactive Services orchestration space, I’m sure that this session is going to be a blast. I’m also thrilled to witness all hilarious ways a 4 presenters demo could go wrong.”
Make sure to listen to Katrin’s session Tuesday, October 4 • 3:10pm – 4:00pm “Microservices: The danger of overhype and importance of checklists”
If you have particular things you are interested in, please reach out to me on twitter or leave a comment. I am really looking forward to the reactive summit. If you haven’t already, there is still some time and we have some seats left! Register today!