Building and operating services distributed across a network is hard. Failures are inevitable. The way forward is having resiliency as a key part of design decisions.
This post talks about two key aspects of resiliency when doing RPC at scale - the circuit breaker pattern, and its power combined with client-side load balancing.
Today we are launching a new API application process.
Starting today, developers will need to fill out an application form to request access to our API.
Here is why.
As SoundCloud has grown, we’ve seen our API used in countless innovative ways that support and enhance the SoundCloud experience for our creators and listeners around the globe. At the same time, we’ve also seen a number of apps or services that act on behalf of our users without their explicit permission or attempt to use creator content in ways that are not permitted by our API Terms of Use. Apps or services that operate in this way do not support our creators, listeners or the SoundCloud community.
Here is what it means.
Developers who currently have API credentials and comply with our API Terms of Use may continue to use the SoundCloud API. All new requests for an API key must go through the review process, where applications will be reviewed on a case by case basis, in line with our API Terms of Use. If your application is successful, you will receive an API key.
To review our API Terms of Use, click here.
If you wish to submit an API Application Form, click here.
In a previous series of blog posts, we covered our decision to move away from a monolithic architecture, replacing it with microservices, interacting synchronously with each other over HTTP, and asynchronously using events. In this post, we review our progress toward this goal, and talk about the conditions and strategy required to decommission our monolith.
About a year ago we faced an interesting question at SoundCloud: can we build SoundCloud Pulse — our app for creators — with React Native? Is a five-month-old technology mature enough to become part of SoundCloud’s tech stack?
As well as adding new features and updates, we review existing features to see if they're still beneficial to the community.
As we dug into the best ways for curators to connect with artists and fans, we found that Groups aren't working as well as reposts and curated playlists.
With that in mind, we've decided to phase out Groups on Monday, August 22nd to make room for future updates.
From this date, all Groups-related GET requests will no longer return results, and PUT requests will not persist any changes.
If your application relies on Groups, please update it by August 22nd, 2016.