Two naive ideas that may be OK as a going-in position: - granularity - bandwidth negligibility Breaking everything down to a gnat's ass might improve testabi

Two naive ideas that may be OK as a going-in position: - granularity - bandwidth negligibility Breaking everything down to a gnat's ass might improve testability, but is testability the product? Do I really need a Java stack trace that reads like an Andrew Wiles proof?[1] Maybe I do, at scale. Then there is the non-zero cost of the packet shuffling. Every edge in the aechitctural graph, not just the nodes, costs. But we just throw a waiter into the code and move on to the next line. No biggie. What was most interesting was "It also increased our scaling capabilities." Granularity was supposed to let "serverless" absorb the entire universe, I thought. At a higher level of abstraction, maybe The Famous Article is a map/reduce job: the requirements dissolved into solution, and a proper number of components precipitated out. [1] https://en.m.wikipedia.org/wiki/Wiles%27s_proof_of_Fermat%27s_Last_Theorem https://en.m.wikipedia.org/wiki/Wiles%27s_proof_of_Fermat%27...