History (or How I Got the UHK)
So it turns out mechanical keyboards are like a drug to me. After I tried my first one at work, I
had to
get more.
At the same time I started to pay attention to the ergonomics of my typing. I noticed that when I
typed a lot, my fingers and wrists would start getting fatigued quickly. My typing style also had
space for improvement, with my left hand stealing a lot of work from the right hand and my fingers
hitting the wrong keys. I was a touch typist, but following my own style that was hardly optimal.
All this got me looking for something different, an ergonomic keyboard.
This post is sponsored by Dotcom-Monitor.
Load testing is an integral part of deploying any web service. It should be
done already in the development phase to find bottlenecks and after deployment
when users' usage patterns are better known. That's not where it stops, though,
as load testing can also be used as a regular part of the web service's
maintenance. Deploying new features without checking their effect on the
performance of the service can be a fatal mistake, which is why load testing
could be very important when integrated with a continuous integration or
continuous deployment system.
In this article, I will review four different load testing services (in
alphabetic order):
Spirent's Blitz.io,
Load Impact,
SendGrid's Loader.io, and
Dotcom-Monitor's LoadView.