Frankenstein's microservices: How to avoid the monster
Many companies adopt microservices to break down monoliths, but they soon uncover a hidden cost: How do you manage all these new interconnected things popping up? Michael Hamrah explains how to avoid creating Frankenstein's monster by understanding elements of a microservice platform. . .so you can sleep at night.
|Talk Title||Frankenstein's microservices: How to avoid the monster|
|Speakers||Michael Hamrah (Namely)|
|Conf Tag||Build resilient systems at scale|
|Location||New York, New York|
|Date||September 20-22, 2016|
Many companies adopt microservices to break down monoliths, but they soon uncover a hidden cost: How do you manage all these new interconnected things popping up? What are good service boundaries? How do you increase reliability when so many more things can go wrong? Microservices can help you decompose a monolith, enable developer velocity for organizations, and help a system scale. Whether consciously or unconsciously, companies that adopt microservices end up building a platform. If you’re not careful, you end up with a distributed monolith or a set of microliths that become unwieldy and reduce reliability and developer velocity. Drawing on his experience building microservices at Getty Images, Uber, and Namely, Michael Hamrah identifies as set of common elements of a microservice platform that go beyond tools and frameworks. Michael helps you reduce risk by discussing the other side of microservices: the platform you create to build, deploy, manage, and understand all the small interconnected things you release to production. Join in to learn how tools like gRPC, Envoy, Spinnaker, and Kafka help you compose your microservice system successfully, what you need to think about when designing services, and how to avoid the pitfalls of a distributed monolith. Avoid creating Frankenstein’s monster by understanding elements of a microservice platform. . .so you can sleep at night.