Today’s cloud-first applications require from the software architect a careful selection of patterns, components and services from a vast catalogue recommended by each cloud provider. The growing number of recommended patterns, components, and services available create the impression that there is already a solution to every problem and the architect is simply required to choose the right combination, very much like a chef’s menu of the day: predefined, non-creative, and budget restricted. But is this truly the case?