Designing High-Availability Distributed Computing Architectures

A practical programme in high-availability distributed architecture for professionals who are accountable for results, not just awareness.

📍 Tripoli🗓️ 5 training days📚 4 modules🎓 Accredited certificate
5intensive training days
4scientific modules
8training sessions
32detailed points

Course Overview

Vendors sell high-availability distributed architecture as a product; it behaves in practice as a change programme. The distance between a working prototype of the digital and data-driven work capability and a system the business can depend on is where most budgets disappear. Comparative studies of this aspect of digital and data-driven work across sectors find the same handful of failure points recurring. The programme converts high-availability distributed architecture from an area of general awareness into a set of repeatable practices. The programme uses small-group work so that each participant's treatment of the digital and data-driven work capability is examined, not just described. It is written for people who have to make the practice within digital and data-driven work work with the resources they already have. The difficulty is not agreeing that high-availability distributed architecture matters — it is deciding what to stop doing to make room for it. Participants develop a defensible line of reasoning for the choices they make about the digital and data-driven work discipline. The final session converts the week's work on this area of digital and data-driven work into commitments with owners and dates.

Expected Learning Outcomes

01

Build a register of the risks attaching to high-availability distributed architecture and keep it current.

02

Define success criteria for high-availability distributed architecture in business terms before any technology is selected.

03

Establish version control and rollback for every component of high-availability distributed architecture that reaches production.

04

Select indicators that show whether high-availability distributed architecture is improving, and reject those that only look useful.

05

Design a practical operating method for high-availability distributed architecture that fits the organisation's size and maturity.

06

Evaluate the bias, fairness and explainability obligations attaching to high-availability distributed architecture.

07

Document the decision record for high-availability distributed architecture so successors understand why it is built this way.

Who Should Attend

01

Information security officers reviewing the exposure created by high-availability distributed architecture.

02

Experienced practitioners formalising an approach to high-availability distributed architecture that has grown up informally.

03

Vendor and contract managers overseeing suppliers involved in high-availability distributed architecture.

04

Operations managers whose processes are changed by high-availability distributed architecture.

05

Operations staff who encounter the consequences of high-availability distributed architecture directly.

06

Solution architects designing how high-availability distributed architecture fits the existing estate.

Course Modules

01

High-availability distributed architecture: architecture, integration and the existing estate

2 sessions · 8 points

Session 1Escalation and decision rights in high-availability distributed architecture

  • Define the exit route from the supplier supporting high-availability distributed architecture.
  • Assess the regulatory obligations high-availability distributed architecture triggers in each jurisdiction.
  • Classify the data in high-availability distributed architecture and apply access controls that match the classification.
  • Confirm the retention and deletion rules applied to data inside high-availability distributed architecture.

Session 2Building lasting competence in high-availability distributed architecture

  • Test the procedure for high-availability distributed architecture against a realistic scenario.
  • Measure the current quality of the data feeding high-availability distributed architecture before assuming it is usable.
  • Agree what will be standardised in high-availability distributed architecture and what will not.
  • List the data sources high-availability distributed architecture consumes and confirm each has a named owner.
02

High-availability distributed architecture: business case, scope and the data it depends on

2 sessions · 8 points

Session 1The pilot that actually settles the argument about high-availability distributed architecture

  • Prepare the summary of high-availability distributed architecture that senior management will read.
  • Identify the skills the team lacks to operate high-availability distributed architecture independently.
  • Verify that high-availability distributed architecture still performs when input volume doubles unexpectedly.
  • Draft the minimum viable delivery roadmap for high-availability distributed architecture.

Session 2Closing out high-availability distributed architecture and capturing what was learned

  • Specify the fallback path when high-availability distributed architecture is unavailable.
  • Identify single points of dependency in high-availability distributed architecture and reduce them.
  • Estimate compute and licensing cost for high-availability distributed architecture at expected and at peak load.
  • Distinguish symptoms from causes when high-availability distributed architecture underperforms.
03

High-availability distributed architecture: governance, ethics and explainability

2 sessions · 8 points

Session 1Sizing high-availability distributed architecture honestly before committing budget

  • Set out the decisions in high-availability distributed architecture that require sign-off and by whom.
  • Define acceptance criteria for high-availability distributed architecture in advance.
  • Identify where judgement in high-availability distributed architecture is legitimate and where it is not.
  • Benchmark the organisation's high-availability distributed architecture against comparable operations.

Session 2The governance high-availability distributed architecture needs and the governance it does not

  • Confirm that those complying with high-availability distributed architecture understand why it exists.
  • Define the service level high-availability distributed architecture must meet and what happens when it is missed.
  • Set the metrics that will show whether high-availability distributed architecture is drifting from its intended behaviour.
  • Record the rationale for each significant choice made about high-availability distributed architecture.
04

High-availability distributed architecture: security, privacy and regulatory obligation

2 sessions · 8 points

Session 1Who owns high-availability distributed architecture once the project team disbands

  • Agree who is on call for high-availability distributed architecture outside working hours.
  • Arrange the handover of high-availability distributed architecture so capability survives staff changes.
  • Remove steps in high-availability distributed architecture that add effort without adding assurance.
  • Set out how exceptions to high-availability distributed architecture are requested and approved.

Session 2Proving high-availability distributed architecture paid for itself

  • Decide which legacy process high-availability distributed architecture retires, and set the date.
  • Plan how high-availability distributed architecture is versioned and how a bad release is rolled back.
  • Identify every system high-availability distributed architecture must read from or write to.
  • Plan the sequence in which improvements to high-availability distributed architecture will be introduced.

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.