Skip to content
axe Tipsaxe TipsUser guides

design.axesuite.com · user guide

axe Design guide

Learn system design by building it. Each problem gives you real traffic, data, a latency and uptime target and a budget; you build it from servers, caches, queues and databases, and the simulator throws peak traffic at it. There is no single right answer: anything that holds up, fast enough, within budget, passes. Open axe Design →

Getting started

Sign in once

Open axe Design and sign in with Google. It's the same sign-in as every axe Suite app, so if you're signed in elsewhere you go straight in.

For You, Problems, Profile

The bar under the nav bar has three sections. For You opens first: Continue (what you've started, with when you last tried, your submissions and the last result), Suggestions (your weakest idea, the next step up, something new) and themed lists. Problems has all 26, searchable and filtered by difficulty and idea. Profile has your numbers, your problems, what trips you up, and every submission.

Any list shows as cards or as a compact list (the switch at the top right); your choice is remembered. Going between sections, or back from a problem, keeps your place.

Read the brief

Open a problem. The brief on the left says what to build: the request types and their traffic at peak, the data and where it may live, the p99 latency for each request, the uptime target and the monthly budget. Each problem has three stages, and the traffic grows with each one.

Building a design

Add components from the dock at the bottom: click one, or drag it onto the canvas. Point at any of them to see what it is. Wire them in the direction requests travel: drag from a component's right-hand dot to another one.

Select a component to set it up on the right: how many servers, replicas, shards, a cache's hit rate, which data a store holds. Each one shows how busy it is under load as you go; red means overloaded.

Tip: Fold either side panel from the button on the panel itself; it shrinks to a rail that still shows the stage, the score and whether you pass. The problem list button (beside Back) searches and switches problems; your board is saved first. Undo and redo with ⌘Z and ⇧⌘Z, fit the view with F.

Run and Submit

Like a coding judge, there are two ways to test.

Run (⌘↵) tests three of the checks in your browser (routing, capacity, latency). It's quick, and nothing is kept.

Submit (⇧⌘↵) is the official test: all six checks, at peak traffic, on the server. Every request routed, nothing overloaded, the data fits, p99 latency within the targets, uptime met, and the monthly cost within budget. It's kept with your submissions, and passing unlocks the next stage.

Tip: The traffic slider in the top bar tries more or less than the peak (×0.5 to ×2) while you build; Submit always tests at ×1.

Submissions and notes

The details panel has three tabs: Load test (the live result as you build), Submissions (every submit, newest first: passed or what failed, score, stars, cost, when) and Notes.

Click a submission to see exactly what you submitted, read-only, with its load test; your current board stays as it is. Each submission has its own note, and the Notes tab is the note on your current attempt; a submission starts with the note you had when you submitted it.

Stages, stars and your profile

Each stage passes with a score and up to three stars. Profile keeps it all: stages and stars, practice time and your streak, a map of the days you practised, your load-test scores, the checks you fail most and your progress on each idea (caching, sharding, real-time…).

The Streaks button in the nav bar shows your streak: a day counts when you practise (build, run or submit).

axe AI as your coach

axe AI sits in the top bar (⌘K). It can look at your board and its load-test result, explain in plain words what failed and why, and give one hint at a time. It never changes your design.

FAQ

Is there one right answer? No. Any design that passes all six checks passes. A sample solution is in the brief if you want to compare; showing it replaces your canvas, and ⌘Z brings yours back.

Does placement matter? No: only the components, their settings and how they're wired.

Is my work saved? Yes, as you go, for each problem.