Microservices Architecture at Spotify

Gonzalo P.
Jul 25, 2016 · 2 min read

Interesting video where Kevin Goldsmith (CTO, Spotify) explains in a general way, how the architecture of Spotify has changed in time in order to escalate. It helps to know how the applications we use on a daily basis work, making us to re-think how we are developing sofware and to start applying new design patterns that are fully tested.

Spotify works with a Microservice architecture, where all software developers code in a closed “territory” with his specific functionalities. Each Microservice have only one simple responsability and in most cases they have a private database with his own logic that cannot be intervened by another process. This gives to the application the ability to escalate quickly, deploying different services in different machines with personalised perfomance depending in the demand of each service.

Suddenly you need to change the logic of some specific feature? No problem! you will just need to modify the specific service that implements the feature, test it and deploy it. Now you will have a new logic that will work with all the others platforms applications that are consuming the service. No need to deploy the entire application, and the best of all, others developers will not be affected by this modification.

But remember, all the services must be small and lightweight. Divide and conquer!

Codebase

Software development obsession. Good practices, tips and interesting stuff about coding

Gonzalo P.

Written by

Codebase

Codebase

Software development obsession. Good practices, tips and interesting stuff about coding

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch
Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore
Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade