Chapter 7

1. The Go interface{} type conveys no useful information about the underlying type. If we use it for representing an argument to a function or a method, we effectively bypass the compiler's ability to statically check the function/method arguments at compile-time and instead have to manually check whether the input can be safely cast into a supported known type.
2. Instead of running the compute-intensive stages locally, we can migrate them to a remote machine with enough computing resources. The respective local stages can then be replaced with a proxy that transmits the local payload data to the remote machine via a remote procedure call (RPC), waits for the results, and pushes them to the next local stage. The following diagram outlines the proposed solution:

3. Each processor function must satisfy the Processor interface, whose definition is as follows:

type Processor...