Aches in your back and neck? Clutter eating up your desktop and desk’s top? Feeling so absorbed in your to-do list that you forget to breathe? You could be suffering from IT job stress. And you’re not alone! Let’s look at ways to identify stress before it gets to be too much, and some helpful tips for letting it go.

It’s surprisingly difficult to find information related to monitoring a distributed network. I think this is because, in part, network pros take the term for granted. We all intuitively know what a distributed network is, and the term is pretty common in conversation. But when you start to think about a precise definition, or even search for one online, things get fuzzy. What exactly makes a network distributed? Is a distributed network fundamentally different from a decentralized network?

When I hear QUIC, my immediate reaction is, “The QUICk brown fox jumps over the lazy dog.” That sentence has been ingrained in me since my first typing classes decades ago! I doubt the creators of QUIC were going for this type of reaction when they put together the name… but the good news is that this isn’t an article on typing. We’re diving into what the QUIC protocol is, how it works and how it’s used, and how it’s going to impact web traffic in the future.

One of the largest challenges with network bandwidth metering is the way traffic flows. Traffic comes in bursts. It’s never a constant, predictable stream of data you can measure once, spec hardware for and be done with (wouldn’t that be nice?!). Instead, you need to account for the dynamic nature of bandwidth utilization and its impact on performance. You’ll never be able to predict every burst of traffic your network experiences.