Devops

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)

small set of instances that get the new build first. For a period of time, instances running the new build coexist with instances running the old build If the canary instances behave oddly, or their metrics go south, then the build is not rolled out to the remaining population todo: ref handling versions - peaceful side-by side running of different versions (src: Book_ release it! - Michael Nygard)

Don’t change runtime instances Destroy and recreate Always start from a stable, known base image (src: Book_ release it! - Michael Nygard) (src: Evolutionary Architecture - 9. Guidelines for Evolutionary Architecture)

Pattern: put all dependencies in a private repository Code (eg. Maven) Pipeline (eg. Jenkins plugins) (src: Book_ release it! - Michael Nygard)

Pattern: split deployment view and runtime view Deployment view Transform sources into binaries Transform binaries into deplotments Runtime view Processes running on machines (src: Book_ release it! - Michael Nygard)

Stability Pattern_ Shed load turn away load we can't complete in time Where? Load balancers How? Health check + SLA a good health check on the first tier of services can inform the load balancer when response times are too high (in other words, higher than the SLA) Model_ health check Own response time services can measure their own response time to help with this. They can also check their own operational state to see if requests will be answered in a timely fashion....

Model_ the three ways Model_ 4 types of work

(src: Book_ The Phoenix Project)

(src: Book_ The Phoenix Project)

Continous Delivery Sounds Great - Jez Humble ( https://www.youtube.com/watch?v=SjVV3xuYKJs ) Model: software = design + delivery design= unpredictable delivery = predictable lean 6 sigma doesn’t fit on software ; because software is 2 things 6 sigma tries to get all variability out of a system great for delivery, not great for design xp lean software development unix inventor of unix pipe (2) = microservices (3) = deliver early & often (4) = automate, tool based...