Logical task combinators

When I had to use Erlang for the very first time it was a brand new language and I was in collage. Back then Erlang did not have a logical not function so we had to define our own in order to make our code readable. At least given the knowledge me and my lab partner had at the time. So the other week I had a deja vu moment since I had a Task<bool> that I wanted to negate. At first it felt real weird and I ended up solving my problem in a different way. But then I started to think.

Comparing two null objects

Maybe it is my experience with databases but I have always thought that whenever you compare something with null it is always false. Obviously there are some exceptions.

Hashtable vs ConcurrentDictionary

Historically I've seen the Hashtable be favored over ConcurrentDictionary with the assumption that is was more efficient allowing for lock free reads. Well they both allow lock free reads so which one is really the better option?

Circuit Breaker Summary

Remember to read the intro.

Circuit Breaker on rate

Remember to read the intro.

Circuit Breaker on concurrency

Remember to read the intro.

Circuit Breaker on failure rate

Remember to read the intro.

Circuit Breaker on number of failures in time window

Remember to read the intro.

Circuit Breaker on consecutive failures

Remember to read the intro.

The Circuit Breaker Pattern

I don't remember where I first heard about the circuit breaker pattern but I had seen it a few times in a few different forms under different names. Over time I have come to believe that the original approach described to me might not be the most appropriate.