Defining API boundaries

We expect platform engineers to compose all the infrastructure and application automation concerns in XR APIs. How to define an API boundary is a bit tricky. It’s because many conflicting trade-off points are influencing the API boundaries. Let’s start with the fact that we wanted to compose every resource required for an application and its infrastructure in a single composition. Here are some considerations that will not allow us to do that:

• There would be many security and architecture policies that need to centralize. We cannot add them again and again in multiple compositions.
• Some resources may have compliance requirements and must be composed separately for audit purposes.
• Overly big compositions are difficult to read, understand, debug, and refactor.
• Testing a bulk composition is difficult.
• Every application will require some customization to the infrastructure recipe, provided we have a bulk composition. We will...