Evolutionary Serverless Architecture: JeffConfg Hamburg 2018 talk

I want to share my JeffConf Hamburg talk with you: Evolutionary Serverless Architecture

[wpcc-element _tag=”source” type=”image/webp” srcset=”/images/2018/04/evolutionary-serverless-architecture@730w.webp 730w, /images/2018/04/evolutionary-serverless-architecture@730w2x.webp 1460w, /images/2018/04/evolutionary-serverless-architecture@610w.webp 610w, /images/2018/04/evolutionary-serverless-architecture@610w2x.webp 1220w, /images/2018/04/evolutionary-serverless-architecture@450w.webp 450w, /images/2018/04/evolutionary-serverless-architecture@450w2x.webp 900w, /images/2018/04/evolutionary-serverless-architecture@330w.webp 330w, /images/2018/04/evolutionary-serverless-architecture@330w2x.webp 660w, /images/2018/04/evolutionary-serverless-architecture@545w.webp 545w, /images/2018/04/evolutionary-serverless-architecture@545w2x.webp 1090w” sizes=”(min-width: 1200px) 730px, (min-width: 992px) 610px, (min-width: 768px) 450px, (min-width: 576px) 330px, 545px” _close=”0″]

A system architecture often struggles to adapt to new requirements. Serverless architectures can evolve because the small building blocks are easier to replace. I demonstrate the concept with an example: our Slack bot marbot. marbot supports your DevOps team to detect and solve incidents on AWS. How and why have we changed the architecture when moving from hackathon to product? How do we ensure that we are on the right track? Watch the talk for answers!

[wpcc-iframe class=”embed-responsive-item lozad” data-src=”https://www.youtube-nocookie.com/embed/KR-cZkLu3ck” allow=”accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture” allowfullscreen=””]

Malwine took visual notes (Sketchnotes) of my talk:

Evolutionary Serverless Architecture: From hackathon to product – by @hellomichibye at #JeffConfHamburg #Sketchnotes pic.twitter.com/mkm5aXatps

— Malwine (@malweene) 16. Februar 2018