:..>Splitting up a monolith into microservices is now becoming a common practice in startups when they reach a certain size. While for most this may be a good choice, it does not come for free. Aside from increased observability, reliability and performance requirements, this approach brings in a number of fresh application vulnerabilities, and re-introduces some old ones. This presentation will attempt to list a few of these, their reasons, and their blast radius, including the risk of some truly impressive cascading failures.

:..>Bio: Tom Czarniecki has been a system breaker, UI developer, devops shaman, microservice architect, AWS trainer and infrastructure architect. He loves making things and breaking things and making things to break things makes him particularly happy. Currently he is the technical lead for application security at DigitalOcean. Previously he was the technical lead and founder of the engineering teams at SoundCloud NYC and before that Tom was a lead consultant at ThoughtWorks for longer than he cares to remember. More info at: https://watchitlater.com/blog/

Comments

Comments are closed.