Video: Microservices at Netflix Scale: Principles, Tradeoffs & Lessons Learned - R. Meshenberg
April 7th, 2019
Microservices at Netflix Scale: Principles, Tradeoffs & Lessons Learned - R. Meshenberg
Principles in action
register to service discopvery
get external stuff from service discovery
-> test it in prod
billing services (needs to be just right)
Need for microservices
1) Contract for intermediate language (IPC)
2) protect your dbs
3) operational visibility
is it scalable? get signal out of noise
Failure, need to test in prod
cf kanban "crash and burn"
containers != microservices
containers at scale
your own context
If chaos kong kills a region, and nobody notices, did it happen?
engineers need to check telemetry regularly
How to decide which services new/remove
Destructive testing on financial parts.
failure will happen
is tech ok?
are ppl ok?
Service visualisation, where can I get it
flux and ...
What discipline do you require from engineers
freedom & responsibility
Cross service functionality