This is the story of how we used the [Strangler pattern](https://martinfowler.com/bliki/StranglerFigApplication.html) to migrate our [public API](https://developers.soundcloud.com/docs/api/explorer/open-api) from a monolithic codebase to a fully fledged [BFF](https://developers.soundcloud.com/blog/service-architecture-1) over the course of eight years. It also discusses some of the trials and tribulations we encountered along the way.

The SoundCloud Blog offers a  content related to music streaming, audio production, and music technology. With a focus on providing insights, updates, and behind-the-scenes stories from the world of music, the blog covers topics such as artist spotlights, industry news, and platform updates. Developers can learn about SoundCloud's APIs and SDKs, as well as best practices for integrating audio streaming and music discovery features into their applications. By following the SoundCloud Blog, developers can stay informed about the latest trends and developments in the music industry and explore opportunities to incorporate music-related features into their projects.

Backstage Blog

SoundCloud started as a single Ruby on Rails application more than 14 years ago. In 2014, we made the decision to not integrate it with other services to serve the public API, but to instead build a Scala service using Finagle. This new service would intercept and augment public API responses by calling additional services when necessary, following the Strangler pattern.

The End of the Public API Strangler