Free tools Windows power users keep installed
One-click scans. No signup required.
ArchPath is presented by its creator, Orest Klymko, as a free system-design course built around an interactive architecture simulator. Learners connect modeled infrastructure components, apply a workload, and watch simulated latency, errors, utilization, and cost change as they alter the design. The course and simulator are described in Klymko’s DEV Community article, displayed as published October 5, 2026.
How the simulator works
The learner builds an architecture on a canvas using components such as servers, load balancers, caches, queues, and databases. After wiring them together, the learner runs traffic through the design and observes how the modeled system responds. Because the simulator is described as deterministic, the same design and workload produce the same outputs, making it possible to change one choice at a time and compare results.
As an Amazon Associate I earn from qualifying purchases.
The output described by Klymko includes latency, errors, utilization for each node, and a monthly bill. That combination can help make design trade-offs visible: a choice that relieves pressure on one component may affect cost or move the bottleneck somewhere else.
What the course covers
Klymko’s article says the course contains 52 topics across 10 acts, plus around 200 production-incident scenarios. Those are the creator’s stated course counts; the article does not provide an independent audit of the catalog.
#1 Best Overall
Incident themes include bad deployments, hot keys, retry storms, and region failures. A sandbox also lets learners shape their own workload, which is useful for exploring how a design behaves when demand or conditions change rather than following only a fixed example.
What the sample numbers do—and do not—show
In one scenario illustrated in the article, traffic doubles and the simulator reports p99 latency above 400 ms and database utilization of 86%. Adding a cache in that same modeled scenario brings reported latency to 140 ms and database utilization to 30%.
These are illustrative simulator outputs, not measurements of real services or independent production benchmarks. The article describes components using modeled properties such as capacity, latency, hit ratio, and cost; it explicitly says there is no real Redis or Kafka behind the simulation. Treat the figures as a way to reason about cause and effect within the model, not as a forecast for a particular production system.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteWho may find this approach useful
A visual, interactive exercise can make it easier to connect architecture choices with their consequences than a diagram alone. ArchPath’s described format may suit learners who want to practice tracing bottlenecks, exploring failure scenarios, or comparing how a workload behaves after a design change.
Rank #3
It is not a substitute for operating real infrastructure. The course article does not establish how closely the simulator’s outputs match deployed systems, nor does it provide independent evaluation of learning outcomes. Use it to build and test mental models, then validate important decisions with the requirements, measurements, and failure behavior of the actual systems involved.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Access and practical details
Klymko describes the course as free and says no account is needed to begin. Progress remains in the browser unless a learner signs up, and the course works best on a laptop. The article does not specify browser compatibility, privacy or data-retention practices, what an account adds, or whether any paid tiers exist; those details should not be inferred from the stated free access.
Quick Recap
Best Value
Rank #4
How to assess it for your own learning
- Check whether the simulator lets you change both the architecture and workload, rather than only view a preset result.
- Look at whether the outputs make the trade-offs you care about visible, including latency, errors, utilization, and cost.
- Keep the model boundary in mind: components are simulated, not connected to live infrastructure.
- If you run production systems or conduct system-design interviews, compare the model’s assumptions and outputs with your own experience. The creator specifically invites feedback on numbers that seem wrong and topics that feel too easy or confusing.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Recommended Free Tools
