Devops

If production user data passes through it, it is production software. If it's main job is to manage other software, it is the control plane (src: Book_ release it! - Michael Nygard)

Which controls (src: Book_ release it! - Michael Nygard)

Heuristic: useful metrics (src: Book_ release it! - Michael Nygard)

if your organization treats load balancers as "those things over there" that some other team manages, then you might even think about implementing a layer of software load balancing under your control (src: Book_ release it! - Michael Nygard)

once we're talking about shutting down more than 50% of total server capacity, the automation probably ought to pause for some human confirmation automation has no judgement We should use automation for the things that humans are bad at: repetitive tasks and fast response. We should use humans for things automation is bad at: perceiving the whole situation at a higher level (src: Book_ release it! - Michael Nygard)

(src: Book_ release it! - Michael Nygard) (origin: https://12factor.net)

page or api call that reveals the application's internal view of it's own health (src: Book_ release it! - Michael Nygard)

throughput time = flow units in process * cycle time eg. time for you to make it through airport security queue = ppl before you * avg time to check a person (src: Book_ This is LEAN - Niklas Modig & Par Ahlstrom)

platform team should provide the capability that others use. monitoring team doesn't do the monitoring it provides the ability for others to do their own monitoring shift from ownership of the domain to offering a service to customers (src: Book_ release it! - Michael Nygard)

push push over network 🙂 containers no long-lived identity no local storage pull central machine reaches out to all known hosts services write to local files (src: Book_ release it! - Michael Nygard)