Top Banner
A People’s History of Microservices Monitoring for the Small Fry Camille Fournier, CTO, Rent the Runway @skamille
48
Welcome message from author
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
Page 1: A People's History of Microservices

A People’s History of Microservices

Monitoring for the Small Fry

Camille Fournier, CTO, Rent the Runway@skamille

Page 2: A People's History of Microservices

@lonelocust

Page 3: A People's History of Microservices

How do we get out of here?

Page 4: A People's History of Microservices

How did we get here?

Page 5: A People's History of Microservices

A People’s History

Well, my muddled memories and impressions of living through the past 20 years of computing evolution

Page 6: A People's History of Microservices

In the beginning…

Page 7: A People's History of Microservices
Page 8: A People's History of Microservices

Leslie Lamport

“A distributed system is one in

which the failure of a computer you

didn’t know existed can render your own computer

unusable”

Page 9: A People's History of Microservices
Page 10: A People's History of Microservices
Page 11: A People's History of Microservices
Page 12: A People's History of Microservices
Page 13: A People's History of Microservices
Page 14: A People's History of Microservices

@cra

Page 15: A People's History of Microservices

@@adrianco

AAAHHHHHHHHH

Page 16: A People's History of Microservices
Page 17: A People's History of Microservices

To Sum Up:

Page 18: A People's History of Microservices
Page 19: A People's History of Microservices

Under conditions of…

Page 20: A People's History of Microservices

SCARCITY

“Should” and “Must” need not apply

Page 21: A People's History of Microservices
Page 22: A People's History of Microservices

This does not require

perfection to reach!

http://martinfowler.com/bliki/MicroservicePremium.html

Page 23: A People's History of Microservices
Page 24: A People's History of Microservices

What is monitoring anyway?

Page 25: A People's History of Microservices

Identify the cause of known problems quickly

Page 26: A People's History of Microservices

Understand the state of systems at all times

(to detect hidden or upcoming problems)

Page 27: A People's History of Microservices

Part 1: Identifying the cause of problems

quickly

And other incident management improvements…

Page 28: A People's History of Microservices

TESTING

Page 29: A People's History of Microservices

THE WISDOM OF INES SOMBRA @RANDOMMOOD

Page 30: A People's History of Microservices

Monitoring is not a substitute for

testing

Seriously, stop saying that. Now. Stop it.

Page 31: A People's History of Microservices

Clearly Articulate Dependencies

What downstream systems does this system rely on?

What does “healthy” look like for the system?

Page 32: A People's History of Microservices
Page 33: A People's History of Microservices

Enabling devs to hand off support of systems is actually good!

Page 34: A People's History of Microservices

What about tools tho?

Page 35: A People's History of Microservices

Pick a couple of tools, no more!

Page 36: A People's History of Microservices

Consistency, Clarity over Creativity

Page 37: A People's History of Microservices

Part 2: Detect and predict things that are wrong without alerts

And operating well enough when things are failed.

Page 38: A People's History of Microservices
Page 39: A People's History of Microservices

Your most useful data is an approximation of your

business

What is the CUSTOMER experiencing?

What is the CLIENT experiencing?

What are the rhythms of your business like?

Page 40: A People's History of Microservices

Your Team

Your Customers

Page 41: A People's History of Microservices

RESILIENCE

Page 42: A People's History of Microservices
Page 43: A People's History of Microservices

Any of your

services can die

Page 44: A People's History of Microservices

User

Checkout

Static Asset CDN Origin

Drupal

Our Runway

Home

Grid

Product Detail

static assets

sinatra views / erbs

< Sinatra::Base

RtR API clients

Heroku

Rackspace

Engine Yard

Page 45: A People's History of Microservices

In conclusion

Page 46: A People's History of Microservices

We’re all in this together

Page 47: A People's History of Microservices

“There is an underside to every age about which history does not often speak, because history is written from records left by the privileged”

Howard Zinn, A People's History of the United States

Page 48: A People's History of Microservices

Thanks! Questions? @skamille