February 2009
Intermediate to advanced
718 pages
22h 43m
English
book
Design – Build – Run: Applied Practices and Principles for Production-Ready Software Development
by Dave Ingram
Content preview from Design – Build – Run: Applied Practices and Principles for Production-Ready Software Development
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
24.2. Separating the Components
During testing and even live service, you're required to deploy updated components. Even if this activity is fully automated, it needs to be verified, which can take time. Verification could involve a combination of manual checks as well as running sample transactions through the system (which would need to be cleared out following the verification tests).
In testing, it is not unusual to deploy a patch or a hot fix to an environment. An issue might arise that needs to be turned around quickly, so instead of deploying a full code release, you deploy a discrete subset of components or libraries. Although this is also true in production sometimes, the operations and service delivery teams will generally want all production servers and environments to be in-sync. For example, consider a simple change in the SystemFramework library. This library would need to be deployed to all the servers across the estate, including the disaster recovery site. If it is not, there is the chance that Version 1 could reside on some servers while Version 2 could reside on another server, as shown in Figure 24-1.
Figure 24.1. Figure 24-1
The operations and service delivery teams are not usually keen to deploy single hot fixes and libraries like this unless it's absolutely necessary for emergency purposes. They'd much rather deploy a full release, knowing that all the ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access
More than 5,000 organizations count on O’Reilly
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.Julian F.
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.Addison B.
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.Amir M.
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.