This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Pulse. Temperature. Blood Pressure. Micro-service systems have emergent properties too.
nearForm & micro-services 50+ production systems. The good, the bad, and the ugly.
What are micro-services? Independent processes that exchange messages.
Messages are fundamental. Message behaviour has emergent properties.
Message flow rate. Easy to measure. Tells you a lot. Independent of services.
Deploy a new micro-service. Does the new version break anything?
Micro-service message patterns. What to measure? Here’s what we’ve found useful…
Actor. A pool of services share message load evenly (round-robin, say).
Subscriber. Many services all listen for the same set of message types.
Chain. An initial message causes a chain of serial message steps.
Tree. An initial message causes a flowering of child messages.
Why? It's the risk, stupid! Monoliths put everybody in danger.
Risk. Reduction can be measured. Leave elimination to Machiavelli.
Our "best practices" for risk. Unit tests; code reviews; standards. Do we have good measures?
Let's attack both sides. And we'll find a way to connect both attacks.
Formal Methods
“Best Practices”Measurement
Dynamic measurement. Measure health of the system. Exposes unknown unknowns.
Formal methods. Correctness proofs are impractical. Incomplete execution traces? FTW!