Microservices is our BFF: why SoundCloud stopped using its own public API for its mobile clients
Please log in to watch this conference skillscast.
In the beginning, SoundCloud mobile and web clients both used SoundCloud's public API, which allowed the company to “be their own customers” when developing their public API. As SoundCloud's mobile and web clients evolved, public API development became a bottleneck for feature development, because mobile and web clients have different needs. To unblock themselves, they introduced BFF (Backend-for-the-Frontend!), a framework to build custom, usecase-oriented APIs which allowed their mobile engineers to develop and maintain their own API (in Scala!). BFF’s goal is to make writing robust, scalable APIs easy. Duana will share with you the wins and learnings in moving to this architecture and how it enabled the company to transition to feature teams at SoundCloud.
YOU MAY ALSO LIKE:
- Building and Leading Remote Teams (Online Meetup on 19th August 2020)
- Accessibility in Flutter (in Online Event on 20th August 2020)
- Skills Matter droidcon London 2019 Wrap Up! (SkillsCast recorded in October 2019)
- Pushing Dynamic Features Your Users Want, As Quick As They Want Them (SkillsCast recorded in October 2019)
Thanks to our sponsors
Microservices is our BFF: why SoundCloud stopped using its own public API for its mobile clients
Duana Stanley
Duana Stanley has been building both public and internal APIs for the last 4 years. At SoundCloud she has built microservices in Ruby, Node.js and Scala. She is now learning Android so she can make changes to the SoundCloud Android App as required by her feature team. She also enjoys making tech accessible for everyone by coaching at RailsGirls and OpenTechSchool events in Berlin.