In this step, additional data points can be quickly added for consideration. In the previous step, 1% difference in cost is not enough to clearly choose which solution is optimal. In a later step, price distribution will also be considered:

Please click the drop-down box that currently shows By Price and change it to By Performance:

The view will change to now prioritize views based on normalized, real-time performance benchmark data. This additional data enables the comparison of multiple solutions based on performance as the priority data set to organize the views and calculate differences. Please confirm the current views match the following screenshot:

Some may have noticed that the view did not change. There are a couple of reasons for this. First, in the bottom-left oval, the performance numbers presented are pulled from Burstorm's ongoing cloud benchmark service that randomly and continuously tests cloud providers in real time. For this scenario, the performance number 15.7 for AWS is greater than the 9.8 for Azure. The AWS performance is greater than Azure and presented on the left. No change in view is needed. Second, there is only a single line item in the solution; none of the data needed to be changed or reordered since AWS is the lowest cost and the highest-performing in this scenario. Again, no change is needed. If Azure was higher-performing with AWS still the lowest cost, this view would have moved Azure to the left side, as it was the higher-performing solution, and prioritized the data based on performance, as indicated in the drop-down list at the top right.

With this additional data, AWS is slightly lower in terms of cost but appears to be significantly faster. The text in the bottom of each oval on the left side will again visually indicate which is best and what the difference between them is. Please see the following screenshot. In this scenario, the difference is 38%:

Pricing did not give much indication of which would be optimal. The infrastructure sizes also appear to be equal, with both showing as 2x8 machines.

Please note, in the scenario when created, the requested infrastructure size was one core and 7 GB of RAM (1x7). The platform automatically corrects to match how products and services are sold by the providers, how they are meant to be consumed, and how the products and services are deployed.

In this scenario, both AWS and Azure would deploy the requested compute resources as a two-core and 8 GB of RAM (2x8) virtual instance. See the following original request from the lab part 1:

Please compare the requested details to the response details from each provider shown as follows: