ACI and the use case

Let’s first revisit the use case we built upon in Chapter 4. Based on this use case, we determined that ACI was a technical fit for us:

Your company provides an e-commerce solution to the market. Your solution is built on a number of different Microsoft Azure Technologies.

Your product manager informs you that they have purchased licensed code to help them process billing statements. This code is an extension of the existing e-commerce platform and has a number of specific characteristics. The billing statement processing is not a continuous process. The processing happens when a customer requests their billing statements, which can happen randomly at any time of day. The processing is a sort of batch process with a peak load and needs to be available on demand. Deploying infrastructure to be continuously running requires considerable resource capacity, which makes it expensive, as the billing statements are generated continuously.

Now, based on...