Once upon a time, we had a single monolith of software, one mothership running everything. At SoundCloud, the proliferation of microservices came from moving functionality out of the mothership. There are plenty of benefits to splitting up features in this way. We want the same benefits for our data as well, by defining ownership of datasets and ensuring that the right teams own the right datasets.
Backstage Blog RSS
June 20th, 2017 Architecture Data A Better Model of Data Ownership By Joe Kearney
December 7th, 2016 Microservices Architecture Finagle Lessons in resilience at SoundCloud By Argha Chattopadhyay
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.
September 23rd, 2016 Announcements API Sign-up Changes By Platform Team
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.
Here is what it means.
If you wish to submit an API Application Form, click here.
August 26th, 2016 Microservices Architecture Microservices and the monolith By Tom Stuart
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.
August 3rd, 2016 React Native Mobile React Native at SoundCloud By Jan Monschke & Peter Minarik
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?