To always be shipping (SPS)

17
@bridgetkromhout To always be shipping… Bridget Kromhout

Transcript of To always be shipping (SPS)

Page 1: To always be shipping (SPS)

Pi @bridgetkromhout

To always be shipping…

Bridget Kromhout

Page 2: To always be shipping (SPS)

Pi @bridgetkromhout

navigating infrastructure choices

Page 3: To always be shipping (SPS)

Pi @bridgetkromhout

Page 4: To always be shipping (SPS)

Pi @bridgetkromhout

Previously, on Platform Tales…

Docker in Production: Reality, Not Hype

Page 5: To always be shipping (SPS)

Pi @bridgetkromhout

Deconstructing a monolithic

Python/Django app into…

(as was the style at the time)

Go microservices

Page 6: To always be shipping (SPS)

Pi @bridgetkromhout

Page 7: To always be shipping (SPS)

Pi @bridgetkromhout

Page 8: To always be shipping (SPS)

Pi @bridgetkromhout

Containerized builds

runs tests

creates versioned deployable artifacts

standardizes development environment

Page 9: To always be shipping (SPS)

Pi @bridgetkromhout

“Great job on those

zero-downtime

blue-green deployments!”

—no CEO ever

Page 10: To always be shipping (SPS)

Pi @bridgetkromhout

tech decisions: a Markov bot against HNprobably not

^

Page 11: To always be shipping (SPS)

Pi @bridgetkromhout

Page 12: To always be shipping (SPS)

Pi @bridgetkromhout

Just because you can…

…doesn’t mean you should.

Page 13: To always be shipping (SPS)

Pi @bridgetkromhout

Page 14: To always be shipping (SPS)

Pi @bridgetkromhout

promises

Page 15: To always be shipping (SPS)

Pi @bridgetkromhout

reasonable constraints

Page 16: To always be shipping (SPS)

Pi @bridgetkromhout

“To always be

shipping, you need a

shipyard”

Bret Mogilefsky of 18F, on cloud.gov

Page 17: To always be shipping (SPS)

Pi @bridgetkromhout

Thank you!