2017-10-02

Spotify: Java Microservices at Scale

Session abstract

Spotify has a long history of using a microservice architecture and has gone through multiple iterations of programming languages and service frameworks. This session explores how Java finally allowed it a stable and scalable runtime and how its Apollo service framework is leveraged for ease of development and consistency over its more than 1,000 production services.

Speaker(s)

Name	Title	Company
Sharat Chander	Director of Product Management	Oracle
Niklas Gustavsson	Principal Architect	Spotify

Session Info

Experience	Session type	Track
Introductory	Conference Session	Java, Cloud, and Server-Side Development

My Notes

Conway’s Law is embraced
Teams design their own services

Microservices

simplicity easy to understand
scope is limited
robustness. If it fails the impact is probably minimal
scalability

What is a service

highly cohesive
API is important
- much more important then the implementation at first
- switching out services should be easy. Rhat means stable API
More than 1700 services
- cross cutting concerns should be kinda uniform
- Appollo

testing is very easy on this kind of code

Deployment

docker
helios but moving to kubernetes
continues deployment to production
canery testing to see if stuff works or not
new services are really easy to create
jenkins for the build

Composing services

Clients
Access Points (AP)
Hermes. Because http gave problems. Problems with having multiple connections on sockets in stead of connection pools
messaging system based on CRMQ (hermes)
- hermes is not open source because HTTP 2 solves all the problems
Service Discovery
- DNS with SRV records
- DNS lookup to get the list of hostnames used
- containers register thenselves
- DNS is scalable to a ridiculous degree