Information Technology and Communications

Designing Distributed Non-Relational Database Architecture

A senior-level treatment of distributed non-relational databases, focused on what changes outcomes.

  • 5training days
  • 4modules
  • 8sessions
  • 32topics
View packages and pricesCourse outline
Designing Distributed Non-Relational Database Architecture
5days

About the programme

Course Overview

Availability targets for distributed non-relational databases are commercial commitments, whatever the engineering team calls them. The documentation for the technology and systems delivery capability is accurate only until the next release. The programme is built to be used, and every section of the practice within technology and systems delivery it covers ends in something applicable. The method assumes participants will be challenged on their handling of distributed non-relational databases and prepares them for it. Teams frequently over-invest in documenting this part of technology and systems delivery and under-invest in testing it. The professional literature on the wider technology and systems delivery agenda converges on a small set of controls that reliably work. The outcome is a practitioner who can hold a position on distributed non-relational databases and revise it on evidence. The material serves both public bodies and commercial organisations dealing with this strand of technology and systems delivery. The closing exercise tests whether the participant's plan for this aspect of technology and systems delivery survives a hostile question.

Expected Learning Outcomes

  • Measure delivery and reliability of distributed non-relational databases with indicators teams trust.

  • Apply access control and least privilege throughout distributed non-relational databases.

  • Verify that improvements to distributed non-relational databases have held six months after they were introduced.

  • Design a training and briefing approach that sustains competence in distributed non-relational databases.

  • Document distributed non-relational databases to the level a new engineer could operate it.

  • Design a practical operating method for distributed non-relational databases that fits the organisation's size and maturity.

  • Apply data protection and retention requirements within distributed non-relational databases.

Who Should Attend

  • IT managers and service owners responsible for distributed non-relational databases.

  • Service desk and support leads handling incidents in distributed non-relational databases.

  • Solution architects designing distributed non-relational databases.

  • Infrastructure and platform engineers operating distributed non-relational databases.

  • Internal auditors reviewing how distributed non-relational databases is designed and operated.

  • Specialists advising senior management on distributed non-relational databases.

Course Modules

Open any module to see its sessions and topics.

01

Distributed non-relational databases: incident response and severity

2 sessions · 8 points

Session 1Setting availability and recovery targets for distributed non-relational databases honestly

  • Agree the smallest change to distributed non-relational databases that would be visibly useful.
  • Agree what will be standardised in distributed non-relational databases and what will not.
  • Assess the exit route from any cloud or vendor dependency in distributed non-relational databases.
  • Document the runbook for distributed non-relational databases to the level a new engineer could use.

Session 2Least privilege in distributed non-relational databases without blocking the work

  • Measure current load on distributed non-relational databases and project it forward twelve months.
  • Restore a backup of distributed non-relational databases in a test environment and time it.
  • Estimate the resource distributed non-relational databases requires to run as designed.
  • Test the failover for distributed non-relational databases rather than assuming it works.
02

Distributed non-relational databases: capacity, performance and load

2 sessions · 8 points

Session 1Moving distributed non-relational databases from approval to execution

  • Close out actions on distributed non-relational databases rather than leaving them open indefinitely.
  • Set out the decisions in distributed non-relational databases that require sign-off and by whom.
  • Rank the weaknesses in distributed non-relational databases by consequence rather than by ease of fixing.
  • Set delivery and reliability indicators for distributed non-relational databases the team trusts.

Session 2Making releases of distributed non-relational databases routine instead of risky

  • Run a load test on distributed non-relational databases at expected peak plus a margin.
  • Build the internal briefing that explains distributed non-relational databases to those affected.
  • Prepare the summary of distributed non-relational databases that senior management will read.
  • Confirm the support model and escalation path for distributed non-relational databases.
03

Distributed non-relational databases: requirements, targets and service levels

2 sessions · 8 points

Session 1Documenting distributed non-relational databases so someone else can operate it

  • Arrange the handover of distributed non-relational databases so capability survives staff changes.
  • Configure alerting on distributed non-relational databases that reflects what users experience.
  • Set escalation thresholds for distributed non-relational databases that work out of hours.
  • Review whether distributed non-relational databases is aligned with the objectives of the technical platform.

Session 2Escalation and decision rights in distributed non-relational databases

  • Rehearse the briefing on distributed non-relational databases that would follow an incident.
  • Identify the single points of failure in distributed non-relational databases.
  • Define incident severity levels for distributed non-relational databases and the response each triggers.
  • Confirm every release of distributed non-relational databases can be rolled back within a defined time.
04

Distributed non-relational databases: documentation, support and handover

2 sessions · 8 points

Session 1The hard cases in distributed non-relational databases and how to reason about them

  • Define acceptance criteria for distributed non-relational databases in advance.
  • Set the review interval for distributed non-relational databases and who attends.
  • Record the technical debt in distributed non-relational databases and schedule repayment.
  • Remove steps in distributed non-relational databases that add effort without adding assurance.

Session 2Retiring the legacy part of distributed non-relational databases

  • State the availability and recovery objectives for distributed non-relational databases as numbers.
  • Apply change control to distributed non-relational databases including emergency changes.
  • Inventory third-party dependencies inside distributed non-relational databases and their update status.
  • Draft the minimum viable technical standard for distributed non-relational databases.

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.

Share this course

🔗 Short link
View packages and prices

✆