May 12, 2018

[design][microservice] Microservices at Netflix scale

Watch note for Microservices at Netflix scale

Microservices

What's the cost?

Make assumptions

Then we could prioritize which is important.

Services should be stateless

  • Not rely on sticky session
  • Chaos testing
  • Verify stateless (kill the instance randomly)

Scale out vs. scale up

  • NoSQL at scale (Cassandra, Scylla)
  • CAP available
    (Local quorum vs. async copy to remote region)

Redundancy and Isolation for resiliency

  • Avoid single point of failure
  • Make more than one of _anything_
  • Isolate the blast radius for any given failure

Destructive testing

    Check check check

Billing services


Arch:
Request Cache!


Consider maintenance efforts

Writing tools for automation, less human involve would be better!

Reliability

Cascading failures
Tools to check microservices failure
Failure has grades. Some low grade failure is OK with backup services.
Tools: Hystrix, or Envoy




Containers



No comments:

Post a Comment

Note: Only a member of this blog may post a comment.