Applications at Scale

Editor's Notes

• #18: NOTES: Earlier I mentioned that Continuous Delivery encompasses developer resources and deployment environments… not just the code. Talk a little about the “resources” side of that statement.
• #19: NOTES: Its more than just self-service portals….Folks want to access deployment environments seamlessly as part of their daily work routine. You want to access it from the tools you already use, and in most cases you don’t need to be exposed to the inner workings of how those environments are getting spun up. If you can provide these on-demand and tailored for the user’s needs… you can eliminate significant wait time. Agility has a REST-based API that is full featured. That includes role-based access rights managed through the API. You can access Agility from a wide range of tools to spin up an unlimited variety of deployment environments…. All of which are fully governed and controlled. These environments are all tracked and versioned as well… so you can share them with other teams, and/or roll back as needed.
• #24: Center = artifact repository. Do this well = version everything. Precise versioning.Product apps…on the left side.Architect producing platforms and infrastructure (ServiceMesh)Configuration has 2 faces: environment independent. Environment specific configuration.Problem? Probably related to a software change. Ask “what changed”? Need a yesterday button with precisely versioned artifacts. (or don’t repair…reprovision).Strong versioning. This scales. A lot of participation of organization to publish change. Apache makes a change. Not everyone will push the update right away. Not on same day. Rolling upgrades instead. Have to have that kind of infrastructure. Zooming into the 80% problem. This is future state. Current state is series of tailored applications. Each LOB has a separate process. No economies of scale. A bunch of small independent units with different processes. Each group on left going to a separate environment in parallel. This x number of LOBs. (Stop 32:09)
• #25: Enterprise organizations can have hundreds of separate pre-production teams…. All of which need access to resources and environments. Providing automated, policy-driven governance is important to efficiently empower these teams with self-service access to the resource (such as platforms and applications) that they need, along with rightplacement to the appropriate sandbox environments. Agility Platform allows you to create and enforce these policies, which are leveraged across the SDLC to give you an end-to-end audit trail. The policy framework is also designed for extensibility… so that policies can be easily created for unique industry or organizational needs. For example… you could create a regulatory policy… such as a requirement that Live test data can only be used on the secure private cloud.….. Or a security policy…. So that external dev contractors can only use external public cloud accounts.
• #29: NOTES: (OSI/SOA refers to the client’s approved Operating System Image / Standard Operation Environment, which includes a range of the client’s patches and client specific utilities. )Traditional data center: this current approach includes 20 days for customer application build and test processes. It is assumed this is consistent across all other approaches as well. Pre-Production Cloud:Reductions mainly in automated provisioning and for design work across all layers.External Cloud Provider (Fujitsu and HP)CSPs were asked primarily for data on their core IaaS services. “Platform” services were not available from the CSPs. OSI/SOE are assumed to be the same as for pre-production cloud, but are likely to be less as an increase in engagement effort and decision gateways would be likely.