Jano González, SoundCloud
Going from a monolithic architecture to microservices it's never a "big bang" migration, you need to keep delivering features to your users so services are extracted as the need arises.
During the transition, teams deal with both the monolith and microservices. The differences in technology and delivery process for both, combined with the decreased attention the monolith receives can decrease the confidence level, slowing down delivery and even planned microservice extractions.
How much to invest in the original monolith? Too little can lead to teams avoiding it, too much means wasting resources in a deprecated component.
This talk summarizes the experience of containerizing our monolith to run it in the same infrastructure as our microservices, using the same delivery process. How this improved confidence in delivery, how it simplified operations and how it enables us in current initiatives like our multi-datacenter architecture. Also, which problems we encountered along the way.
Jano González, SoundCloud
Jano worked during the last 5 years as a backend engineer at SoundCloud, extracting services from its original monolith and becoming one of the monolith's main maintainers. He currently works for the same company in an SRE role. He eats his own dog food by publishing tracks on https://soundcloud.com/janogonzalez and https://soundcloud.com/velvetsystem82
Open Access Media
USENIX is committed to Open Access to the research presented at our events. Papers and proceedings are freely available to everyone once the event begins. Any video, audio, and/or slides that are posted after the event are also free and open to everyone. Support USENIX and our commitment to Open Access.
author = {Jano Gonz{\'a}lez},
title = {Containerizing Your Monolith},
year = {2019},
address = {Portland, OR},
publisher = {USENIX Association},
month = oct
}