Moving to Microservices at SoundCloud with Lukasz Plotnicki

The page introduces an episode about SoundCloud’s move from a monolithic architecture toward microservices. It says the company benefited from rapid development with a monolith, then had to address the technical debt that followed. Lukasz Plotnicki joins Jeff to discuss the realities of that transition and the lessons SoundCloud learned.

Reading notes

#

• SoundCloud experienced the rapid development benefits of a monolith, along with the long-term technical debt it created.
• The episode focuses on the realities of moving from a monolith to a microservices architecture.
• Lukasz Plotnicki is identified as a consultant and software engineer at ThoughtWorks.
• The listed questions ask about SoundCloud’s application requirements, Rails and monolithic growth, the gradual move to microservices, the impact of multiple front-end interfaces, the difference between a BFF and a microservice, the downsides of BFFs, and the lessons from the case study.