Skip to content

Instantly share code, notes, and snippets.

@dwdraju

dwdraju/Microservice-Failure.md

Last active June 23, 2018 09:25
Show Gist options
  • Save dwdraju/5bed140b4f6f6a8ed39a4d1a51c2c742 to your computer and use it in GitHub Desktop.
Save dwdraju/5bed140b4f6f6a8ed39a4d1a51c2c742 to your computer and use it in GitHub Desktop.
Download ZIP
Microservice Failure
Raw
Microservice-Failure.md
  • Dynamic environments and distributed systems - like microservices - lead to a higher chance of failures.
  • Services should fail separately, achieve graceful degradation to improve user experience.
  • 70% of the outages are caused by changes, reverting code is not a bad thing.
  • Fail fast and independently. Teams have no control over their service dependencies.
  • Architectural patterns and techniques like caching, bulkheads, circuit breakers and rate-limiters help to build reliable microservices.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment