More about this pattern.

It is actually quite common to see this pattern now-a-days using events. Something like CancelEventArgs and a CancelEventHandler to handle the FormClosing event of a Form.

We use Chain of Responsibility in RavenDB in several places, like this one:

    foreach (var requestResponderLazy in currentDatabase.Value.RequestResponders)
    {
      var requestResponder = requestResponderLazy.Value;
      if (requestResponder.WillRespond(ctx))
      {
        var sp = Stopwatch.StartNew();
        requestResponder.Respond(ctx);
        sp.Stop();
        ctx.Response.AddHeader("Temp-Request-Time", sp.ElapsedMilliseconds.ToString("#,# ms", CultureInfo.InvariantCulture));
        return requestResponder.IsUserInterfaceRequest;
      }
    }

Note that we have moved on the the behavioral patterns, and those tend to have withstand the test of time much better, in general.

Other places where Chain of Responsibility is used is request routing and error handling. A common approach is to also have this done by delegating, where I am handling what I can and passing on to the next object if I don’t know how to handle a request.

Recommendation: This is still a very useful pattern. One thing to note is that it is effectively an O(N) operation with respect to the number of items in the chain that you have. As usual, do not overuse, but it is a really nice pattern.