SoundCloud Achieves High Performance, Exponential Growth with Help from New Relic
Company Size
200-1,000
Region
- America
- Europe
Country
- Bulgaria
- Germany
- United Kingdom
- United States
Product
- New Relic
Tech Stack
- Ruby
- Java
- Scala
- Clojure
- Go
- Haskell
- Amazon Elastic Compute Cloud (EC2)
Implementation Scale
- Enterprise-wide Deployment
Impact Metrics
- Customer Satisfaction
- Productivity Improvements
Technology Category
- Analytics & Modeling - Real Time Analytics
- Application Infrastructure & Middleware - API Integration & Management
Applicable Industries
- Telecommunications
Applicable Functions
- Discrete Manufacturing
- Product Research & Development
Use Cases
- Predictive Maintenance
- Real-Time Location System (RTLS)
Services
- Cloud Planning, Design & Implementation Services
- Data Science Services
About The Customer
Launched in 2008 by Alexander Ljung and Eric Wahlforss, SoundCloud is a social sound platform that gives users unprecedented access to the world’s largest community of music and audio creators. Committed to ‘unmuting’ the web, SoundCloud allows everyone to discover original music and audio, connect with one another, and share their sounds with the world. Sound creators can use the platform to instantly record, upload and share sounds across the internet, as well as receive detailed stats and feedback from the SoundCloud community. The company has offices in Berlin, London, Sofia, and San Francisco and employs 180 people.
The Challenge
When Tobias Schmidt joined SoundCloud in 2011, he was struck by the sheer size of the company’s code base. With 15 - 20 coders all developing different parts of the code base, it was extremely difficult for anyone, especially a new employee, to understand that much code and how it might behave in a production environment. Usage on the site was growing exponentially month over month, and Schmidt’s team was constantly pushing out new features to keep pace with user demand. In many cases, that meant creating code to meet an urgent need, then leaving it untouched for months or even years. SoundCloud’s early features worked perfectly well for a small number of users. But in many cases, those same features wouldn’t scale as users became more numerous and more active. All of those coding changes, often made under intense pressure and in response to increased demand, made it difficult for the SoundCloud team to identify which lines of code might be the cause of poor site performance. Prior to using New Relic, team members would often email each other to diagnose any given problem, relying on limited internal data to achieve a very slow, very incomplete picture of the issue at hand.
The Solution
In 2009, SoundCloud’s web-serving HTML application was built entirely on Ruby. They identified an urgent need to monitor site performance in what was, at the time, an exclusively Ruby environment. New Relic was the only legitimate Ruby monitoring solution on the market, and SoundCloud didn’t have the resources to develop their own solution. Implementation was easy from the start, and continues to be a cinch even as the company’s development environment grows increasingly complex. SoundCloud relies on a number of New Relic features to maintain the best possible service for millions of active users of the social sound platform. These features help Schmidt and his team locate problems and identify trends as they emerge, enabling SoundCloud engineers to prioritize their work with an appropriate sense of urgency. Even as SoundCloud makes significant changes to its development environment, New Relic will continue to take the lead in diagnosing performance issues.
Operational Impact
Quantitative Benefit
Case Study missing?
Start adding your own!
Register with your work email and create a new case study profile for your business.
Related Case Studies.
Case Study
Vodafone Hosted On AWS
Vodafone found that traffic for the applications peak during the four-month period when the international cricket season is at its height in Australia. During the 2011/2012 cricket season, 700,000 consumers downloaded the Cricket Live Australia application. Vodafone needed to be able to meet customer demand, but didn’t want to invest in additional resources that would be underutilized during cricket’s off-season.
Case Study
SKT, Construction of Smart Office Environment
SK T-Tower is the headquarters of SK Telecom. Inside the building, different types of mobile devices, such as laptops, smartphones and tablets, are in use, and with the increase in WLAN traffic and the use of quality multimedia data, the volume of wireless data sees an explosive growth. Users want limitless Internet access in various places in addition to designated areas.