Building Modern Web Applications with Microservice Architecture

An applied course in microservice web applications built around the decisions practitioners actually face.

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

Course Overview

Security and delivery speed are traded against each other in microservice web applications whether or not anyone says so. Most outages involving the wider technology and systems delivery agenda are triggered by a change somebody considered routine. Participants come from operational and oversight roles, and both perspectives on the technology and systems delivery capability are used deliberately. Across sectors, teams that rehearse microservice web applications outperform teams that only plan it. Each session closes with a decision the participant must justify about this strand of technology and systems delivery in their own setting. Teams frequently over-invest in documenting the practice within technology and systems delivery and under-invest in testing it. The outcome is a practitioner who can hold a position on microservice web applications and revise it on evidence. It treats this strand of technology and systems delivery as an operating discipline and equips participants to run it as one. The course ends by identifying what the participant will stop doing to make the technology and systems delivery capability sustainable.

Expected Learning Outcomes

01

Prepare a short, evidence-based briefing on microservice web applications for senior management.

02

Measure delivery and reliability of microservice web applications with indicators teams trust.

03

Design the architecture of microservice web applications around its failure modes, not only its happy path.

04

Manage change to microservice web applications so every release can be rolled back.

05

Review contracts and agreements for the obligations they create around microservice web applications.

06

Recognise early indicators that microservice web applications is drifting away from its intended design.

07

Apply access control and least privilege throughout microservice web applications.

Who Should Attend

01

Infrastructure and platform engineers operating microservice web applications.

02

Analysts producing the data on which decisions about microservice web applications rest.

03

Project managers delivering changes to microservice web applications.

04

Service desk and support leads handling incidents in microservice web applications.

05

Network and communications engineers supporting microservice web applications.

06

Members of committees that take decisions affecting microservice web applications.

Course Modules

01

Microservice web applications: change control and rollback

2 sessions · 8 points

Session 1The paperwork for microservice web applications that is actually needed

  • Confirm every release of microservice web applications can be rolled back within a defined time.
  • Estimate the resource microservice web applications requires to run as designed.
  • Test the failover for microservice web applications rather than assuming it works.
  • Document the runbook for microservice web applications to the level a new engineer could use.

Session 2Least privilege in microservice web applications without blocking the work

  • Record the rationale for each significant choice made about microservice web applications.
  • Review access rights on microservice web applications and remove what is no longer needed.
  • Apply change control to microservice web applications including emergency changes.
  • Map the handovers in microservice web applications between functions and secure them.
02

Microservice web applications: capacity, performance and load

2 sessions · 8 points

Session 1Making microservice web applications work when resources are constrained

  • Restore a backup of microservice web applications in a test environment and time it.
  • Record what was learned when microservice web applications did not go as planned.
  • Review logging on microservice web applications for coverage and retention.
  • State the availability and recovery objectives for microservice web applications as numbers.

Session 2Running an incident on microservice web applications calmly

  • Configure alerting on microservice web applications that reflects what users experience.
  • Assess the exit route from any cloud or vendor dependency in microservice web applications.
  • Define incident severity levels for microservice web applications and the response each triggers.
  • Confirm data retention and deletion rules applied within microservice web applications.
03

Microservice web applications: architecture and designing for failure

2 sessions · 8 points

Session 1Making releases of microservice web applications routine instead of risky

  • Benchmark the organisation's microservice web applications against comparable operations.
  • Run a load test on microservice web applications at expected peak plus a margin.
  • Rank the weaknesses in microservice web applications by consequence rather than by ease of fixing.
  • Set out how exceptions to microservice web applications are requested and approved.

Session 2Building lasting competence in microservice web applications

  • Verify six months later that changes to microservice web applications have held.
  • Record the technical debt in microservice web applications and schedule repayment.
  • Set the review interval for microservice web applications and who attends.
  • Define acceptance criteria for microservice web applications in advance.
04

Microservice web applications: documentation, support and handover

2 sessions · 8 points

Session 1Retiring the legacy part of microservice web applications

  • Agree the indicators that will show whether microservice web applications is improving.
  • Close out actions on microservice web applications rather than leaving them open indefinitely.
  • Decide what will be stopped to create capacity for microservice web applications.
  • Set delivery and reliability indicators for microservice web applications the team trusts.

Session 2Documenting microservice web applications so someone else can operate it

  • Prepare the summary of microservice web applications that senior management will read.
  • Confirm the support model and escalation path for microservice web applications.
  • Establish what evidence demonstrates microservice web applications is under control.
  • Confirm that those complying with microservice web applications understand why it exists.

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.