Microservices at Netflix Scale • Ruslan Meshenberg • GOTO 2016

This presentation was recorded at GOTO Amsterdam 2016. #gotocon #gotoams

Ruslan Meshenberg - Director of Platform Engineering at Netflix @RuslanMeshenberg-q7h

FULL TALK TITLE
Microservices at Netflix Scale - First Principles, Tradeoffs & Lessons Learned

ABSTRACT
Netflix's world leading streaming service is comprised of hundreds of microservices. We will cover explicit technology choices we made for all of the microservices to work well together, and the lessons learned of things that don't work well. We will describe the organizational structure inside of Netflix [...]

Download slides and read the full abstract here:

RECOMMENDED BOOKS

#Microservices #Scaling #ScalingSoftware #RuslanMeshenberg

CHANNEL MEMBERSHIP BONUS
Join this channel to get early access to videos & other perks:

Looking for a unique learning experience?

SUBSCRIBE TO OUR CHANNEL - new videos posted almost daily.

[GOTO-]

Looking for books & other references mentioned in this video?
Check out the video description for all the links!

Want early access to videos & exclusive perks?

Question for you: What’s your biggest takeaway from this video? Let us know in the comments! ⬇

[CrustyPea]

Things I learned from this talk:
- microservice ops requires a lot of good quality tooling
- adoption of microservices requires big/gradual change towards teams fully responsible for their own services
- must do destructive testing in production env to really understand resilience of system

[reneetsielepi]

Very useful insights and lessons learned, too often case studies show just how quick and easy it is which makes you think you're taking too long. Very honest and reassuring! Thank you.

[guddurajakharshitachoudhar]

I like their way of learning from nature and putting it to software development cycle. Great Stuff and Great evolutionary thought. It's sure nothing work for ever, it evolves and as per need, the architecture need to evolve, to do business.

[sbylk]

From monolith to micro scervices, org change is the hardest part. Prove my intuition.

[berkarslan]

Great video. One thing that confused my mind is that he stated that RDBMS in the previous infrastructure was single point of failure. Imo, as long as you don't replicate the data somewhere else (and sometimes even that's not enough) or cache the entire data storage, the data storage will always will be single point of failure. What did change in new architecture so that it's not single point of failure now?? If it's about each and every microservices can use it's own data storage principle, lets assume that's true. As long as you didn't abstract the environment these microservices work on, they most probably will use the same DB Servers, DB Engines etc. What then? As long as your db server is not lightweight (and I mean VERY lightweight), you cannot install a new db engine for each microservices (can you imagine installing 100 SQLServer instances..)

What I mean is solving single point of failure in data storage aspect does not seem very suitable for me in real world. Theoretically possible though..

[quarkorion]

Nice video, but a small correction at the time 30:41 / 48:33: (0.99^500) * 100 = 0.657% (not 0.0657% as shown)

[bpfurtado]

I saw a talk with the CTO of Deutsche Bank regarding microservices and I really cannot find, was it on GOTO or is my memory mistaken?

[BryanStetson]

Very informative! +1 for the Frank Underwood sticker on the speaker's laptop.

[marwooj]

Hi, what is the software used to mix video and slides in this way that they are using on goto;?

[giladbaruchian]

How do you make each team independent of other teams? often one team needs to use other team's service

[crashpointXzero]

Very insightful. Thanks for sharing your experience. especially the parts about org changes.

[techwithbasil]

This was quite informative. Very useful insights for implementing microservices

[awanbiru-ride]

Very true, most of failures happened during weekends. Lol

[chihabahmed]

Hi there, if i multiple services that they work independently ( will they still be called microservice)?

[redbenus]

Triggering failures. Like fire drills with real fire. IT beating its old analogy of construction/building ...

[kls]

43:22 architecting is not a single-person function. its a culture.

[minbenja]

2:31 over 500? pff come back to the talk when its over 9000 =P

[tr]

Microservices are crazy, but if the salary good, you just dont give a dam.