Define the scope and boundaries of serverless computing strategy so that responsibility for it is unambiguous.
Designing Serverless Computing Strategies for Elastic Applications
A structured, applied course in serverless computing strategy — designed to be used the week you return.
Course Overview
Technical debt in serverless computing strategy is borrowed against future delivery capacity, at compound interest. Systems supporting the technology and systems delivery discipline fail in ways that are obvious afterwards and invisible before. It is designed for mixed groups, so that this aspect of technology and systems delivery is examined from more than one functional angle. The course gives participants a defensible structure for serverless computing strategy and the judgement to adapt it. A common pattern is strong design of the practice within technology and systems delivery paired with weak follow-through. Mature organisations treat the wider technology and systems delivery agenda as a standing capability rather than a project that finishes. Each session closes with a decision the participant must justify about serverless computing strategy in their own setting. Participants develop a defensible line of reasoning for the choices they make about the technology and systems delivery capability. Work concludes with a self-assessment of this area of technology and systems delivery that participants can repeat annually.
Expected Learning Outcomes
Assess and manage third-party and cloud dependencies in serverless computing strategy.
Design the architecture of serverless computing strategy around its failure modes, not only its happy path.
Build the deployment pipeline for serverless computing strategy so releases are routine rather than events.
Sequence improvements to serverless computing strategy so that each step makes the next one easier.
Diagnose whether a problem in serverless computing strategy is one of design, resourcing or discipline.
Measure delivery and reliability of serverless computing strategy with indicators teams trust.
Who Should Attend
IT governance and audit staff reviewing serverless computing strategy.
Service desk and support leads handling incidents in serverless computing strategy.
Infrastructure and platform engineers operating serverless computing strategy.
Team leaders and supervisors who put serverless computing strategy into practice day to day.
Procurement and contracting staff whose agreements set obligations around serverless computing strategy.
Quality and test engineers verifying serverless computing strategy.
Course Modules
Serverless computing strategy: requirements, targets and service levels
2 sessions · 8 pointsSession 1Making releases of serverless computing strategy routine instead of risky
- Establish who is informed, consulted and accountable in serverless computing strategy.
- Set delivery and reliability indicators for serverless computing strategy the team trusts.
- Compare the cost of serverless computing strategy with the cost of its absence.
- Establish the boundary of serverless computing strategy and record what sits outside it.
Session 2Retiring the legacy part of serverless computing strategy
- Review logging on serverless computing strategy for coverage and retention.
- Arrange the handover of serverless computing strategy so capability survives staff changes.
- Document the runbook for serverless computing strategy to the level a new engineer could use.
- Apply change control to serverless computing strategy including emergency changes.
Serverless computing strategy: documentation, support and handover
2 sessions · 8 pointsSession 1Setting availability and recovery targets for serverless computing strategy honestly
- Run a load test on serverless computing strategy at expected peak plus a margin.
- Identify the single points of failure in serverless computing strategy.
- State the availability and recovery objectives for serverless computing strategy as numbers.
- Record the rationale for each significant choice made about serverless computing strategy.
Session 2Getting other functions to support serverless computing strategy
- Test the failover for serverless computing strategy rather than assuming it works.
- Reduce the variation in how serverless computing strategy is carried out between teams.
- Prepare the summary of serverless computing strategy that senior management will read.
- Confirm the support model and escalation path for serverless computing strategy.
Serverless computing strategy: change control and rollback
2 sessions · 8 pointsSession 1Monitoring serverless computing strategy from the user's point of view
- Confirm every release of serverless computing strategy can be rolled back within a defined time.
- Define incident severity levels for serverless computing strategy and the response each triggers.
- Confirm data retention and deletion rules applied within serverless computing strategy.
- Check that serverless computing strategy still works when volumes rise unexpectedly.
Session 2Making serverless computing strategy work when resources are constrained
- Benchmark the organisation's serverless computing strategy against comparable operations.
- Record the technical debt in serverless computing strategy and schedule repayment.
- Agree the indicators that will show whether serverless computing strategy is improving.
- Restore a backup of serverless computing strategy in a test environment and time it.
Serverless computing strategy: security, identity and least privilege
2 sessions · 8 pointsSession 1Designing serverless computing strategy around how it will fail
- Set the review interval for serverless computing strategy and who attends.
- Establish what evidence demonstrates serverless computing strategy is under control.
- Identify where judgement in serverless computing strategy is legitimate and where it is not.
- Rehearse the briefing on serverless computing strategy that would follow an incident.
Session 2What has to be agreed before work on serverless computing strategy starts
- Confirm that reporting on serverless computing strategy reaches the people who can act.
- Review access rights on serverless computing strategy and remove what is no longer needed.
- Measure current load on serverless computing strategy and project it forward twelve months.
- Distinguish symptoms from causes when serverless computing strategy underperforms.
Choose the package that suits you
Silver Package
At least 3 people
- Workshop or Program Participation
- Airport Transfers
- Customized Badge
- Expert Mentorship (Private Sessions)
- Supervision & Secretarial Services
- Accredited Certificate of Participation
- Complete Training Kit
- Coffee Break
- Closing Ceremony
Gold Package
At least 3 people
- 5-night stay in a 5-star hotel
- Workshop or Program Participation
- Airport Transfers
- Customized Badge
- Expert Mentorship (Private Sessions)
- Supervision & Secretarial Services
- Accredited Certificate of Participation
- Complete Training Kit
- Coffee Break
- Closing Ceremony
Complete your registration
We will contact you within one business day to confirm.