Microservices at Spotify • Kevin Goldsmith • GOTO 2015
Вставка
- Опубліковано 23 лип 2024
- This presentation was recorded at GOTO Berlin 2015. #gotocon #gotober
gotober.com
Kevin Goldsmith - Vice President, Engineering at Spotify
ABSTRACT
The software industry used to be all about building monoliths: monolithic applications and services, with bing-bang product releasees. All that has now changed [...]
Download slides and read the full abstract here:
gotocon.com/berlin-2015/presen...
RECOMMENDED BOOKS
Sam Newman • Monolith to Microservices • amzn.to/2Nml96E
Sam Newman • Building Microservices • amzn.to/3dMPbOs
Ronnie Mitra & Irakli Nadareishvili • Microservices: Up and Running• amzn.to/3c4HmmL Mitra, Nadareishvili, McLarty & Amundsen • Microservice Architecture • amzn.to/3fVNAb0
Chris Richardson • Microservices Patterns • amzn.to/2SOnQ7h
Adam Bellemare • Building Event-Driven Microservices • amzn.to/3yoa7TZ
Dave Farley • Continuous Delivery Pipelines • amzn.to/3hjiE51
/ gotober
/ gotoconference
#Microservices #BreakingUpMonoliths #SoftwareArchitecture
Looking for a unique learning experience?
Attend the next GOTO conference near you! Get your ticket at gotopia.tech
Sign up for updates and specials at gotopia.tech/newsletter
SUBSCRIBE TO OUR CHANNEL - new videos posted almost daily.
ua-cam.com/users/GotoConf... - Наука та технологія
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!
Awesome...spotify videos are the best...the one (in two parts) on Agile, Squads, Chapters, Guilds is my all time fav on UA-cam...
I was joyed to see the view aggregation. I wondered if you used a specification language (in the VA) for building UI capabilities?
Great talk!
If i had 600 developers i would do microservices as well
Informative talk ;) Thx
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.
Thanks,
Nice video.
21:52 Service Routes?
nicely explained !!
Spotify has a Bieber service hahahaha
Very useful video for education 🤘🏻
i like it, nice.. Thanks
Someone knows the lamp he is talking?
i quickly thought LAMP stack
"AWOX StriimLight WiFi"
Sorry but that German joke was the cutest thing ever
So much effort designing the system, but apparently no effort to come up with a consistent and clear naming policy?
I can't believe that managers allowed them to name services like "Ice-cream!"
what do you know? and why does it matter? I obviously works for them and they don't seem hindered by it.
guy looks like hasnt slept in months
Party hard!
good talk but really really very bad delivery.guy is sounds so sleepish
1.5 speed
Nice talk, but a bit disappointed that you use Java in Production. There are better choices.
+Siddharth Kulkarni Interesting. Especially from the scaling perspective: which ones?
+BLUE SCRUM Scala?
+Thomas Vodrazka Well, Scala is compiled to Java byte code running on JVM. So you agree that Java is a good solution?
+BLUE SCRUM Yeah, there a point of view matter. But regarding scaling perspective Scala does a great job.
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.