>training an operations team to take over maintenance of a nested spaghetti of random interlinked services and bits of YAML trapped in random parts of the cloud

>training an operations team to take over maintenance of a nested spaghetti of random interlinked services and bits of YAML trapped in random parts of the cloud is a total nightmare. The amount of documentation required and even the simple overhead of enumerating every dependency is a long term management burden in its own right. Upon learning about it some time ago, this was exactly my conception of what a Lambda-like serverless architecture would yield. And it would seem difficult, if not impossible, for any dev to maintain a mental map of the architecture.