~/talk

Measuring Micro-services

Talkat Codemotion Rome 2015 · 2015-03-25..03-28· [observability, microservices]
slides:none on file

Argues that risk is reducible by measuring emergent behavior rather than CPU: track message flow rates and invariant ratios (e.g., add-item vs tax messages should be 1:1) and use partial deployments to validate changes (example: five login services, 20% routed to new version). Uses formal specs like TLA+ invariants (Amazon used ~700-line spec and found a bug by exploring 35 steps), and practical tooling such as InfluxDB / Kafka / New Relic plus the Seneca Node.js framework.

AI-written summary · about

  1. 0:00Introduction and health analogy
  2. 2:53What are micro-services?
  3. 10:05Message flow patterns
  4. 13:40Risk reduction with micro-services
  5. 20:08Measuring systems in production
  6. 24:32Formal methods and invariants
  7. 33:04Conclusion and future steps
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.