MicroServices notes: Difference between revisions
From Federal Burro of Information
Jump to navigationJump to search
| Line 35: | Line 35: | ||
==== Data persistance ==== | ==== Data persistance ==== | ||
CAP theorem - In the event of a network partition the trade off between consistency and availability. | |||
==== Infrastructure ==== | ==== Infrastructure ==== | ||
Revision as of 14:37, 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.
