The Practice of Cloud System Administration: Designing and Operating Large Distributed Systems, Volume 2 by Thomas A. Limoncelli (2014-09-13)
Format: PDF / Kindle (mobi) / ePub
ideal is users having a web experience that is faster than with native software applications on a PC, the way to measure our distance to the ideal would involve measuring page load time. If the ideal envisions a world with no security breaches, the way to measure how far we are from that ideal would be the count of known security breaches detected each month. The ideal might also be that all detected intrusions are investigated within a certain time frame, in which case we would quantify both the
review systems, 269 defined, 120 disasters. See Disaster preparedness Overflow capacity factor in service platform selection, 67 Overload failures DoS and DDoS attacks, 139 load shedding, 139 scraping attacks, 140–141 traffic surges, 138–139 Oversubscribed systems defined, 53 spare capacity, 125 PaaS (Platform as a Service), 51, 54–55 Packages build phase, 204 configuration, 220 continuous delivery, 190 deployment phase, 213 distributing, 266 as handoff interface, 207–208
by another internal service or team). (Section 7.3) • Upgrades: Deploying new software releases and hardware platforms. The better we can do this, the more aggressively the company can try new things and innovate. Each new software release is built and tested before deployment. Tests include system tests, done by developers, as well as user acceptance tests (UAT), done by operations. UAT might include tests to verify there are no performance regressions (unexpected declines in performance).
making the users aware that they must move. Sometimes it is a technical issue of moving them to another service. User data may need to be moved or archived. Resource deallocation can cover many aspects. There may be DNS entries to be removed, machines to power off, database connections to be disabled, and so on. Usually there are complex dependencies involved. Often nothing can begin until the last user is off the service; certain resources cannot be deallocated before others, and so on. For
compiles and functions as desired. 9.3.2 Commit During the commit step, the files being developed are uploaded to the source repository. Generally this is done infrequently, as it indicates the files have reached a certain level of completeness. All committed code should be working code. If not, other developers’ work will come to a halt. They will pull recent changes into their workspaces and the result will be code that doesn’t work. They will not be able to tell if the problem is due to