Idempotency is one of my favorite things in all of computing.
It’s kind of like a warm safety blanket that assures you that
“If at first you don’t succeed, try, try, try again”.
Idempotency is one of my favorite things in all of computing.
It’s kind of like a warm safety blanket that assures you that
“If at first you don’t succeed, try, try, try again”.
Martin Kleppmann’s Designing Data Intensive Applications is sure to have you
quietly applauding on your couch, if your mind works anything the same as mine does
(namely, assuming that everything that can go wrong will).
Several years ago while driving through Nebraska in the middle of the night, a curious idea struck me.
“We have systematic testing for software, and for hardware, but why not for networking?”
Lucky for me, I was also searching for a thesis topic at the time.
Most networks are carefully hand tuned and watched over by experienced network engineers and IT personnel. Unfortunately this leaves them vulnerable to human error, configuration mistakes, or rot from “moves, adds, and changes”.