[adamch]

I work on network services, but generally my server's requests start on a user's computer, get to my service, get proxied to some upstream destination elsewhere on the internet, and then the responses flow back. Point is, I work with networks, but generally the latency and throughput is bottlenecked somewhere outside my code. Probably by the user's internet connection, or the server's.

So it was _really_ interesting to listen to this podcast live and think about truly high performance networking. When your requests and responses are all within one rack on your data center, the bandwidth, latency and throughput bottlenecks are MUCH more likely to be your code and hardware. So Oxide has to think about all these high-performance use-cases that I've never once had to stop and think about.

This episode felt like peeking behind the curtain into forbidden knowledge. Great episode.

[bcantrill]

Glad you enjoyed it! And yes, agreed there is so much here that isn't spoken of very broadly: part of what we have loved about social audio is allowing engineering teams to speak candidly about the work that they're doing -- and we're hoping that others follow suit, as I (selfishly) would love to listen to similar conversation from other engineering teams...