Microservices in Practice
summary
SoundCloud migrated from a Rails monolith to small, independently deployable microservices by extracting logic only when large changes required it, keeping a thin service layer inside the monolith and an internal API to avoid big-bang rewrites. The platform — handling 12 hours of audio uploaded every minute — uses Cassandra for high-write domains, HTTP and AMQP for communication, event publication for deletes, feature-flagged progressive rollouts, circuit breakers, per-client BFFs, monitoring, and eventual-consistency patterns to prevent cascades and enable fast testing and deployment.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 3:58Monolith problems
- 7:47Microservices defined
- 13:11Migrating to microservices
- 18:38Handling cascading failures
- 23:16Summary








