Interesting! We're currently migrating our platform to Azure, we are currently hosting many of our Azure Service Bus consumers in Azure functions (I'm currently working on decomposing one of our legacy web APIs to Azure HTTP trigger functions right now, actually.) I agree that there are principles that are similar, but the actual techniques and patterns are different - down to the most core design pattern of the simulation, the "game loop." It is pretty much relegated to games and simulations, and almost no enterprise system uses it, and that pattern informs all others in game architecture. Maybe once I've gotten a few games under my belt I might feel different, but right now they have very different approaches, and very different problems to solve. This also doesn't change my opinion that Unity is a great transition tool for an enterprise developer to a game developer.