Manage change to isolated container environments so every release can be rolled back.
Building Isolated Container Environments for Microservice Applications
A structured, applied course in isolated container environments — designed to be used the week you return.
📍 Tripoli🗓️ 5 training days📚 4 modules🎓 Accredited certificate
5intensive training days
4scientific modules
8training sessions
32detailed points
Course Overview
Most outages involving isolated container environments are triggered by a change somebody considered routine. The documentation for this strand of technology and systems delivery is accurate only until the next release. The course leaves participants able to diagnose weaknesses in this part of technology and systems delivery before they become incidents. The programme takes participants through isolated container environments end to end, from framing the problem to closing it out. Mature organisations treat the practice within technology and systems delivery as a standing capability rather than a project that finishes. Plans for the technology and systems delivery discipline often fail at the handover point between functions. Each session closes with a decision the participant must justify about isolated container environments in their own setting. It is written for people who have to make this area of technology and systems delivery work with the resources they already have. The programme ends where implementation begins, with the technology and systems delivery discipline broken into steps someone can start on Monday.
Expected Learning Outcomes
Build the deployment pipeline for isolated container environments so releases are routine rather than events.
Diagnose whether a problem in isolated container environments is one of design, resourcing or discipline.
Control technical debt in isolated container environments deliberately rather than by neglect.
Translate policy on isolated container environments into procedures that hold up under day-to-day pressure.
Establish what evidence would demonstrate that isolated container environments is under control.
Build incident response for isolated container environments with defined severity and escalation.
Who Should Attend
Database administrators managing data within isolated container environments.
Managers with direct responsibility for isolated container environments within the technical platform.
Service desk and support leads handling incidents in isolated container environments.
IT managers and service owners responsible for isolated container environments.
Managers of multi-site operations seeking consistency in isolated container environments.
Project managers delivering changes to isolated container environments.
Course Modules
Isolated container environments: security, identity and least privilege
2 sessions · 8 pointsSession 1Setting availability and recovery targets for isolated container environments honestly
- Plan the sequence in which improvements to isolated container environments will be introduced.
- Decide what will be stopped to create capacity for isolated container environments.
- Record the technical debt in isolated container environments and schedule repayment.
- Measure current load on isolated container environments and project it forward twelve months.
Session 2Documenting isolated container environments so someone else can operate it
- Configure alerting on isolated container environments that reflects what users experience.
- Confirm that those complying with isolated container environments understand why it exists.
- Restore a backup of isolated container environments in a test environment and time it.
- Prepare the summary of isolated container environments that senior management will read.
Isolated container environments: incident response and severity
2 sessions · 8 pointsSession 1Reading the current state of isolated container environments honestly
- Define acceptance criteria for isolated container environments in advance.
- Build the internal briefing that explains isolated container environments to those affected.
- State the availability and recovery objectives for isolated container environments as numbers.
- Apply change control to isolated container environments including emergency changes.
Session 2Dependencies and supply chain risk in isolated container environments
- Document the runbook for isolated container environments to the level a new engineer could use.
- Confirm data retention and deletion rules applied within isolated container environments.
- Identify the single points of failure in isolated container environments.
- Confirm the support model and escalation path for isolated container environments.
Isolated container environments: capacity, performance and load
2 sessions · 8 pointsSession 1Building the method for isolated container environments step by step
- Record what was learned when isolated container environments did not go as planned.
- Arrange the handover of isolated container environments so capability survives staff changes.
- Review access rights on isolated container environments and remove what is no longer needed.
- Agree the smallest change to isolated container environments that would be visibly useful.
Session 2Retiring the legacy part of isolated container environments
- Remove steps in isolated container environments that add effort without adding assurance.
- Set escalation thresholds for isolated container environments that work out of hours.
- Test the failover for isolated container environments rather than assuming it works.
- Review logging on isolated container environments for coverage and retention.
Isolated container environments: monitoring, alerting and observability
2 sessions · 8 pointsSession 1Proving the backup of isolated container environments by restoring it
- Identify the data already collected that bears on isolated container environments.
- Anticipate the objections isolated container environments will raise and prepare the answers.
- Build the competence framework that supports isolated container environments.
- Reduce the variation in how isolated container environments is carried out between teams.
Session 2Reviewing isolated container environments when nothing has gone wrong
- Run a load test on isolated container environments at expected peak plus a margin.
- Establish the boundary of isolated container environments and record what sits outside it.
- Set delivery and reliability indicators for isolated container environments the team trusts.
- Confirm every release of isolated container environments can be rolled back within a defined time.
Choose the package that suits you
Silver Package
At least 3 people
USD1,250
- 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
USD1,850
- 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.