MicroServices notes: Difference between revisions
From Federal Burro of Information
Jump to navigationJump to search
(→Hybrid) |
|||
| Line 45: | Line 45: | ||
==== Stateful ==== | ==== Stateful ==== | ||
==== Hybrid ==== | ==== Hybrid ==== | ||
caching layer is hybrid | |||
consider VCache, a system for managing memcache and spymemcached | |||
https://github.com/Netflix/EVCache | |||
=== Variance === | === Variance === | ||
=== Change === | === Change === | ||
Revision as of 14:57, 30 May 2019
Mastering Chaos - A Netflix Guide to Microservices - Notes
Evolutionary response
- Separation of concern: modularity and encapsulation
- Scalability: horizontal, and partitioning
- Virtualization and Elasticity - automation, and on demand capacity
Dependancy
Use cases:
Intra-Service Requests
can handle non ideal issues
- network issues
- back off
- handling failure.
- can protect against one service failing?
Hystrix
FIT - Fault Injection Testing
Graceful degradation - testing the removal of things, some less important, some more.
Client libraries
Bare bones , or client libraries?
Data persistance
CAP theorem - In the event of a network partition the trade off between consistency and availability.
Infrastructure
Scale Use Cases
Stateless
Stateful
Hybrid
caching layer is hybrid
consider VCache, a system for managing memcache and spymemcached
https://github.com/Netflix/EVCache
