BFF Pattern in Action: SoundCloud’s Microservices
•
4 likes•3,902 views
At SoundCloud we managed to break away from the monolith while delivering key business features. Our journey towards a microservices architecture has not been a straightforward one. We experimented a lot to reach the set of tools and technologies that we use today. We changed how we build our applications. We introduced specific apis for our mobile and web clients. We call them BFFs (backend for the frontend). They became the central piece of SoundCloud’s architecture. We rethought how we monitor our services. We created a service registry for knowledge sharing. While making all these changes, we benefited from the learnings of our peer companies. This talk will share our learnings from this journey: what worked for us and what we moved away from.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to BFF Pattern in Action: SoundCloud’s Microservices
Similar to BFF Pattern in Action: SoundCloud’s Microservices (20)
Recently uploaded
Recently uploaded (20)
BFF Pattern in Action: SoundCloud’s Microservices
- 2. BFF Pattern in Action SoundCloud’s Microservices
- 3. Bora Tunca Joined SoundCloud 2.5 years ago soundcloud.com front-end client specific apis core-services @grandbora
- 4. SoundCloud is the largest online audio distribution platform
- 5. 12 HOURS OF AUDIO every minute
- 8. MOTHERSHIP
- 17. Humane Registry
- 18. Oriented around people Humane Registry
- 19. Oriented around people Don't rely on people to stay up to date Humane Registry
- 20. Oriented around people Don't rely on people to stay up to date Expect humans to read and contribute Humane Registry
- 26. Api-v2 Api-mobile Api-embedded Public API
- 27. Api-v2 Api-mobile Api-embedded Public API messages MOTHERSHIP likes search stats images
- 28. Api-v2 Api-mobile Api-embedded Public API Edge Layer messages MOTHERSHIP likes search stats images
- 29. Api-v2 Api-mobile Api-embedded Public API Edge Layer Client Applications Microservices messages MOTHERSHIP likes search stats images
- 32. Microservices
- 35. BFF
- 36. BFF authentication geo location features 1
- 44. messages MOTHERSHIP BFF likes search stats images authentication geo location features BFF BFFBFF BFFBFF
- 45. messages MOTHERSHIP BFF likes search stats images authentication geo location features BFF BFFBFF BFFBFF Critical Path
- 47. Be ready for traffic bursts On critical path…
- 48. Be ready for traffic bursts Handle failures gracefully On critical path…
- 58. images userstracks Foundation Layer playlistsstream profiles Value Added Layer
- 59. images userstracks Foundation Layer playlistsstream profiles Value Added Layer
- 60. images userstracks Foundation Layer playlistsstream profiles Value Added Layer
- 61. BFF BFF images userstracks Foundation Layer playlistsstream profiles Value Added Layer
- 62. BFF BFF images userstracks Foundation Layer playlistsstream profiles Value Added Layer MOTHERSHIP
- 65. GRAPHITE STATSD
- 67. Prometheus Scalable data collection Operational simplicity Multi-dimensional data Powerful query language https://developers.soundcloud.com/blog/prometheus-monitoring-at-soundcloud http://prometheus.io/
- 68. Prometheus
- 75. Prometheus My Service jvm client My Service jvm client My Service jvm client My Service jvm client My Service jvm client My Service jvm client My Service jvm client My Service jvm client My Service jvm client My Service jvm client
- 77. val requestCount = telemetry.counter("outgoing_http_requests_total", "A counter for the HTTP requests", "service", "method", "status", "statusClass") send requestCount .labels( serviceName, request.getMethod, response.getStatus, response.getStatusClass ).inc()
- 78. val requestCount = telemetry.counter("outgoing_http_requests_total", "A counter for the HTTP requests", "service", "method", "status", "statusClass") send requestCount .labels( serviceName, request.getMethod, response.getStatus, response.getStatusClass ).inc() query SUM(rate(outgoing_http_requests_total{statusClass!="2xx"}[10m])) by (service, method, status)
- 84. manifest.json { "name": "trackmetadata", "type": "internal_service", "description": "Track Metadata service", "contact_email": "xxxxxxx", "owner": "core-services", "status": "production", "alert_service": "pagerduty.com/xxxx", "telemetry_dashboard": "http://promdash/trackmetadata", "data_sensitivity": xxxx, "dependencies": xxxx, "slo": { "error_rate_threshold": 0.1, "latency_p99_threshold_seconds": 0.02, "availability_target": 0.99999, "metrics_server": "http://prometheus/trackmetadata" } }
- 85. manifest.json { "name": "trackmetadata", "type": "internal_service", "description": "Track Metadata service", "contact_email": "xxxxxxx", "owner": "core-services", "status": "production", "alert_service": "pagerduty.com/xxxx", "telemetry_dashboard": "http://promdash/trackmetadata", "data_sensitivity": xxxx, "dependencies": xxxx, "slo": { "error_rate_threshold": 0.1, "latency_p99_threshold_seconds": 0.02, "availability_target": 0.99999, "metrics_server": "http://prometheus/trackmetadata" } }
- 86. manifest.json { "name": "trackmetadata", "type": "internal_service", "description": "Track Metadata service", "contact_email": "xxxxxxx", "owner": "core-services", "status": "production", "alert_service": "pagerduty.com/xxxx", "telemetry_dashboard": "http://promdash/trackmetadata", "data_sensitivity": xxxx, "dependencies": xxxx, "slo": { "error_rate_threshold": 0.1, "latency_p99_threshold_seconds": 0.02, "availability_target": 0.99999, "metrics_server": "http://prometheus/trackmetadata" } }
- 87. manifest.json { "name": "trackmetadata", "type": "internal_service", "description": "Track Metadata service", "contact_email": "xxxxxxx", "owner": "core-services", "status": "production", "alert_service": "pagerduty.com/xxxx", "telemetry_dashboard": "http://promdash/trackmetadata", "data_sensitivity": xxxx, "dependencies": xxxx, "slo": { "error_rate_threshold": 0.1, "latency_p99_threshold_seconds": 0.02, "availability_target": 0.99999, "metrics_server": "http://prometheus/trackmetadata" } }
- 89. RECAP
- 91. RECAP Knowledge sharing Evolving the architecture
- 92. RECAP Knowledge sharing Evolving the architecture Monitoring
- 93. backstage.soundcloud.com @pcalcado - How we ended up with microservices @starcoffe - Why SoundCloud stopped using its own public API InfoQ - Moving from a Monolith to Microservices at SoundCloud
- 94. Netflix API Gateway Pattern http://techblog.netflix.com/2013/01/optimizing-netflix-api.html