1. 9
  1.  

  2. 2

    It’s interesting how these are just common performance patterns, but made trivial to implement with channels. As a concurrency primitive, channels are just ridiculously useful. This solution also prevents replication of work, unlike a naive memcache solution where as soon as the cache expires, multiple requests to generate the same content will be processed, a nice touch.