Learning Functional Programming in Go

All parties must participate

In order to reap the full benefits of non-blocking execution all parts in a request/response chain needs to participate in the non-blocking asynchronous call. If any resource, whether inside or outside the service boundary blocks, then we’ve got a problem.

What’s the problem with blocking?

Usually resources provide access via a processing thread. Threads are limited. If all the threads are busy, subsequent requests must wait until one becomes available.

Asynchronous message passing helps us focus on workflows and interaction patterns between our services.