Translating features from ACI to ACA

Our next challenge is to translate the ACI configuration to ACA to make sure we can run our solution without impediments.

ACI configuration for the original use case

For ACI, we had the following configuration set up, as we discussed in Chapter 4:

• A container group per customer
• A billing statement API per container group
• A public endpoint for the customer to call and request billing statements

As the use case becomes extended over time and new requirements are added, our ACA configuration may look similar, but it is, in fact, different.

ACA configuration for an extended use case

Let’s take a look at what configuration in ACA we need, according to our new use case:

• A container app environment per customer, as this will be the “secure boundary” our customers require
• Two container apps per environment, one for the web frontend and one for the API
• Ingress configuration per environment...