Slide deck from my presentation at Leetspeak 2014 on how Spotify builds backend services.

1. Spo$fy'services

2. ngn@spo'fy.com-@protocol7

3. Microservices1*in*anger
1"h$p://mar+nfowler.com/ar+cles/microservices.html

4. Why?

5. Monoliths

6. Simplicity
Robustness

7. Scalability

8. UNIX%philosophy
"Rule&of&Modularity:&Developers&should&build&a&program&out&of&
simple&parts&connected&by&well&defined&interfaces,&so&problems&are&
local,&and&parts&of&the&program&can&be&replaced&in&future&versions&to&
support&new&features.&This&rule&aims&to&save&@me&on&debugging&
complex&code&that&is&complex,&long,&and&unreadable"
—"Eric"S."Raymond,"The"Art"of"Unix"Programming

9. Embrace(Conway's(law2
2"h$ps://labs.spo.fy.com/2014/03/27/spo.fy8engineering8culture8part81/

10. What's'a'service?

11. Let's&walk&a&request

12. Perimeter'services

14. View%services

15. Service'discovery

16. $ dig _spotify-search._hm.lon3.spotify.net SRV +short
5000 5000 8181 lon3-search-a1.lon3.spotify.net.
5000 5000 8181 lon3-search-a2.lon3.spotify.net.
...

17. Data$services

18. Orchestra)on

19. Scaling(out

20. Geographical,distribu2on3
3"h$ps://www.youtube.com/watch?v=JEpsKnWZrJ8

21. Mul$site

22. Failure(modes

23. Failure(modes
Cascading)failures

24. Failure(modes
Build&for&failure

25. Failure(modes
Drop%requests

26. Infrastructure+automa.on

27. Monitoring

28. Outro

29. Ques%ons
ngn@spo'fy.com-@protocol7