With a focus on solo hackers' TS & Go projects.

Polishing up my knowledge on how networking is structured in AWS

Networking services

Optimising Mean Time To Recovery is more important than trying to minimise Mean Time Between Failures.

Something I learnt today. Maybe more than one thing👾Linux infra & logging stuff

I studied networking once upon a time, and I need to brush up those lessons as they're applicable to AWS Solutions Architect learnings.

How Route 53 uses Shuffle Sharding to improve availability when assigning customers to virtual name servers.

Some notes from the Well-Architected Framework whitepaper