Skill · Architecture · Read and analyze a services architecture
Analyze an architecture's entry point: proxies, load balancing and edge
Tell apart on a diagram a web server, reverse proxy, forward proxy, L4 or L7 load balancer, API gateway, ingress, CDN and web application firewall, and spot an entry point's single point of failure or bypass.
Start lesson 1The Architecture domain
- 4 lessons
- ~2 h 25 of reading
- 4 quizzes
- 0 proof lab
The path
Where it comes from, where it leads
What you need to know first, where you stand on this skill, and what it opens next. Your status is computed in your browser, from what you have read and passed.
Before · no prerequisite
A foundation skill: you can start right away.
Recommended before · 1
This skill, for you
Analyze an architecture's entry point: proxies, load balancing and edge
Computing
It unlocks · nothing yet
No other skill requires it: it is an end-of-path skill.
The path through the foundations From the most upstream foundation to this skill: what is in place, what remains to read.
Lessons
How to learn it
4 lessons, about ~2 h 25, in program order. Each lesson ends with its quiz.
The program
4 lessons · ~2 h 25
Beyond the lessons
Assess, practise, pass the proof
Reading a lesson confirms nothing. A skill is confirmed by a passed quiz, practised in a guided lab, and put to the test by a challenge or a mission; an imported lab result is not verified by the site.
Assess yourself
4 quizzes
At the end of the lessons: passed at 70%, they confirm the skill.
Practice
No guided lab
No guided lab practices it yet.
Proof
No proof
Neither a challenge nor a mission with a proof yet.
Placement test
Preparing the questions…
Your answers in detail
For each question asked: your answer, the correct answer, its explanation and the page to reread.
Around it
Who requires it, who teaches it
Required by
No published job requires it yet.
Taught by
Same block · Read and analyze a services architecture
- Read an architecture diagram: role, flows, state and dependencies of each component
- Classify an architecture's data and decide what to back up or replicate
- Follow an architecture's asynchronous exchanges and predict their failures
- Identify an architecture's cross-cutting dependencies and trust boundaries
- Assess how an architecture is operated: recovery, admin access, detection and impact