> There's still a point where it's beneficial to split an application into seperate stacks Do you mean like having a different "infrastructure manifest" for ea

> There's still a point where it's beneficial to split an application into seperate stacks Do you mean like having a different "infrastructure manifest" for each micro-service? In that case, couldn't each micro-service specify which other micro-service it depends upon? For example, I could have a central "API gateway" service which would specify all the other micro-services it depends upon. This reminds me a bit of a Gemfile/Package.json but for processes instead of libraries. On the other hand, I can easily see how this could turn into a dependency hell.