#NightOfCode with the Cohort 2 of MiniHack is underway.NightOfCode is an overnight session where @AvaxAfrica readies the Cohort for final presentations via a trial run & handson support where Team1 identifies gaps that they need to fill. Excited to see their Gamified solutions.
Tracing alone doesn't cut it at scale.
In big tech like uber for example, you can't trace every request, so it's sampled. A rare path between two services may just never show up.
A topology map aggregates traffic over time, not one request, catching what sampling misses.
Assume a Service in a microservice arch breaks in prod at 3am.
Logs tell you something failed. Traces show one request's path. Neither tells you what depends on what across the whole system
A live service topology map does. What breaks if X goes down? becomes an answer not a gues
My landing page for [insert-cool-name-here] is coming along nicely.
Was able to knock this out with Codex.
This would've taken me quite some time pre-AI.