I built a realistic prod system under heavy pressure where you SSH in and solve real problems. You get your own server (real box) and have to fix various things up under fire.
a friend told me it reminded them of DOOM for SREs, another called it a "flight simulator" because you can do anything (and reboot if you crash). someone else said it was like "an escape room for engineers", in that you have to find your own way around an unfamiliar box and solve puzzles. idk, maybe it's fun. try it!
how it works: you get two Hetzner servers: a traffic generator (real traffic from NYC taxi data highly compressed to 12k rps) firing tons of requests at a user server, which has some (realistically) broken stuff trying to get that data to a chart. your job is to get it working and get the whole system latency down. You can use whatever tools or techniques you like to do so.
so far I've seen people messing around in databases, adding caching, rewriting services in go. There's no one right solution!
why I'm building it: I was a school teacher 15 years ago and have been training developers for the last 10. most dev training (tutorials, toy projects &c) feels nothing like the "real job". I wanted to see if we can make training more realistic, challenging, fun.
a friend told me it reminded them of DOOM for SREs, another called it a "flight simulator" because you can do anything (and reboot if you crash). someone else said it was like "an escape room for engineers", in that you have to find your own way around an unfamiliar box and solve puzzles. idk, maybe it's fun. try it!
how it works: you get two Hetzner servers: a traffic generator (real traffic from NYC taxi data highly compressed to 12k rps) firing tons of requests at a user server, which has some (realistically) broken stuff trying to get that data to a chart. your job is to get it working and get the whole system latency down. You can use whatever tools or techniques you like to do so.
so far I've seen people messing around in databases, adding caching, rewriting services in go. There's no one right solution!
why I'm building it: I was a school teacher 15 years ago and have been training developers for the last 10. most dev training (tutorials, toy projects &c) feels nothing like the "real job". I wanted to see if we can make training more realistic, challenging, fun.