Tag: availability

Description

The goal of the course is to outline key concepts, principles, and approaches that are used to design highly loaded systems where performance, scalability, and availability are first-class quality attributes.

By the end of this course, candidates will have acquired in-depth knowledge about how to describe business requirements, how to design a highly loaded system, and how to create a proper test plan.

Key concepts covered in this course

  • Different metrics used to quantify performance, scalability, and availability, such as response time, percentiles, latency, steady-state availability, resource utilization, etc.
  • How to properly formulate and collect business requirements pertaining to a high load system, which must include at least a stimulus and a measurable response for a particular workload and under a specific working mode.
  • Architectural styles that might be used while designing a high load system, with their pros and cons (e.g. microservices, event-driven, command query responsibility segregation, serverless, lambda).
  • Architectural tactics to achieve performance (e.g. caching, batching, lazy loading, throttling, optimistic locking, back pressure, etc.), scalability (e.g. data push, data pull, distributed and parallel processing, etc.) and availability (e.g. replication, redundancy, disaster recovery, circuit breaker, bulkheads, etc.)
  • Advanced development techniques such as thread affinity, NUMA, large pages, false sharing, Data-Oriented Design, C-states, RamFS/TmpFS, memory access patterns, lock-free algorithms, etc.
  • How to elaborate a test plan with a focus on stress, endurance, and load testing

 

Agenda

  • High load system concept (performance, scalability, and availability)
  • High load system requirements: identifying non-functional requirements for high-load systems
  • High load system architecture design pertaining to high performance, highly scalable and high available tactics and anti-patterns
  • High load system development
  • High load system testing
  • Examples of high load systems (e.g. Linkedin use case, Uber use case, etc.)

 

Duration

  • 16 hours

 

Target Audience

  • software developers
  • technical leaders
  • software/solution architects
  • test engineers
  • business analysts with a technical background or passionate about technology

 

Attendees’ Feedback

Excellent course content helping me to understand a lot of things, from a very high level and abstract to a very deep and technical perspective.
I recommend this course if you want to get in touch with real technical topics. The trainer clearly explained to them, even for less technical people.
The trainer was very well prepared. He answered all of our questions, even if they were not really the subject of the training.
I liked more the advanced part about how to tune an application, outside of the programming language, to get better performance.
Interesting and informative course, presented by a trainer who knows a lot of stuff. I got a lot of ideas and techniques that I can use to build more efficient applications in my daily job.

 

People from the following companies attended my courses:

 

Enroll

Note: At the moment this course is available only for companies, teams, or groups of students. The individual subscription (i.e. single person) is not an option at the moment.

 

Description

  • The course introduces the main concepts and context of software architecture. Participants will learn about practices such as essential requirements identification, architectural design, architectural documentation, and architecture analysis.
  • It provides a clear understanding of the main aspects of being a software architect, as well as different types of architects (e.g. enterprise, solution, software, and system).
  • It reveals a structured way of collecting and documenting the business requirements with an architectural impact (i.e. non-functional requirements) to be quantifiable, measurable, and testable.
  • It includes various design techniques in light of the Quality Attributes which help to create software architecture.
  • It teaches you how to create proper and structured architectural documentation, in compliance with its purpose and beneficiaries (i.e. users).
  • Evaluating software architecture should be part of each project, hence we will discuss different techniques that might help you to mitigate the architectural risk.
  • It gives a recipe to conduct a healthy evaluation across different frameworks and libraries which might fit the project, to pick up the most suitable and appropriate based on the environmental context.
  • The course is a blend of lectures, individual and team exercises, and interactive workshops.

 

Agenda

  • Architectural context and main concepts, the role and responsibilities of a software architect
  • Stakeholders, Business Goals and Quality Attributes (e.g. scalability, performance, security, availability, testability, modifiability, usability) in lights of architectural tactics
  • Designing software architecture
  • Documenting the software architecture via viewpoint-based approach and architectural views (how to structure the architectural description)
  • Evaluation of the software architecture involving different types of stakeholders
  • Technologies and frameworks from an architectural perspective (what they mean and how to properly choose them)

 

Duration

  • 16 hours

 

Target Audience

  • software developers
  • technical leaders
  • software/solution architects
  • test engineers
  • business analysts with a technical background or passionate about technology

 

Attendees’ Feedback

I liked the structure of the course, the fact that we applied the concepts we learned by following a methodology creating an architecture starting from the requirements.
The course helped me understand the architectural concepts and the role of an architect.
The course helped me to learn the terminology better, by doing exercises, also with book recommendations, describing architectural tactics and generic patterns.
I was clarified regarding the diagrams (views and viewpoints) and regarding the applicability of some quality attributes.
The trainer is a true professional. He explained everything in detail as best as he could.
I think that diagrams are most useful. I think that they should be implemented for every project and presented to developers when they see a project for the first time, as it is easier to imagine and understand how a project works.

 

People from the following companies attended my courses:

 

Enroll

Note: At the moment this course is available only for companies, teams, or groups of students. The individual subscription (i.e. single person) is not an option at the moment.