Microservices at Spotify • Kevin Goldsmith • GOTO 2015

[@NimTheHuman]

This is one of the most valuable software-engineering-related talks I've ever watched. I'm grateful that we live in a time where companies are open about their org and code architecture/practices. Thank you, Kevin, Spotify, and "go;to" Conference! It would also be interesting to hear from an actual engineer from Spotify (who's in the trenches writing code). "10 services per squad" sounds like a lot of context switching for a single employee. 😅 Some key points from this talk: 9:38 - I loved this illustration of the vertical teams. 11:10 - key slide. 25:10 - another key slide. 26:56 - I didn't fully understand this slide, but it was interesting to see. Seems complex though (for a team of 6 devs). 31:06 - Those were some really good questions from the audience and insightful answers from Kevin!

[@Akhil2481]

Awesome...spotify videos are the best...the one (in two parts) on Agile, Squads, Chapters, Guilds is my all time fav on KZbin...

[@joachimdietl6737]

If i had 600 developers i would do microservices as well

[@KaGeN102]

Spotify has a Bieber service hahahaha

[@Eliecerhdz]

Was the system page where services are listed using a Dota2 icon?? ;). Ez presentation BTW! I really loved it, because IMO you learn more about something like microservices based on showcases of enterprises you know and use, like Spotify, and yes they are very active with Open Source projects and giving feedback to the world about the technology they use. Great enterprise, great product and all works using microservices.

[@ThePeterHayman]

I was joyed to see the view aggregation. I wondered if you used a specification language (in the VA) for building UI capabilities?

[@the.abhisheksinha]

nicely explained !!

[@remexllee]

Great talk!

[@vipulchowkekar9297]

Very useful video for education 🤘🏻

[@lukaslukac8680]

Informative talk ;) Thx

[@guedim1982]

Thanks, Nice video.

[@HialeahLiam]

Sorry but that German joke was the cutest thing ever

[@cafecomjava]

Someone knows the lamp he is talking?

[@ThePeterHayman]

i quickly thought LAMP stack

[@wesleybercx2653]

"AWOX StriimLight WiFi"

[@milosstojanovic747]

21:52 Service Routes?

[@ayushrawat4825]

i like it, nice.. Thanks

[@skeletalbassman1028]

So much effort designing the system, but apparently no effort to come up with a consistent and clear naming policy?

[@krezzie7420]

I can't believe that managers allowed them to name services like "Ice-cream!"

[@VictorMartinez-zf6dt]

what do you know? and why does it matter? I obviously works for them and they don't seem hindered by it.

[@cerberuspandora]

guy looks like hasnt slept in months

Party hard!

[@SiddharthKulkarniN]

Nice talk, but a bit disappointed that you use Java in Production. There are better choices.

[@bluescrum]

+Siddharth Kulkarni Interesting. Especially from the scaling perspective: which ones?

[@Fane89]

+BLUE SCRUM Scala?

[@bluescrum]

+Thomas Vodrazka Well, Scala is compiled to Java byte code running on JVM. So you agree that Java is a good solution?

[@Fane89]

+BLUE SCRUM Yeah, there a point of view matter. But regarding scaling perspective Scala does a great job.

[@bluescrum]

We may have to differentiate between the platform (JEE) and the language (Java). The discussion about Scala vs. Java is about using the same platform, but a different language to create bytecode. So if you have a look at the "billions of servers and devices" Java as a platform is working on there's no alternative to me at the moment from the scaling perspective. That's no real limitation, because today we can chose the language to create bytecode for it. That makes the development more flexible without leaving the secure ground that exists for decades now. So if you like to program in PHP you can do this and use JEE as your scaling platform. And even better: everything can be deployed in pretty short time to a cloud environment.

[@ranbirs2980]

good talk but really really very bad delivery.guy is sounds so sleepish

[@marting1219]

1.5 speed