"You've been asked to architect a new web$-$based e$-$commerce system. Our stakeholders have given us the following requirements:

Customers must be able to search for products by keyword and a host of other product attributes $($brand$,$ category, price range, product type$)$

Customers must be able to pay with a credit card $($our stakeholders have been non$-$specific about any type of payment processor; you have latitude to suggest$)$

After checking out, customers must be emailed a receipt with a summary of their order

In addition to these requirements, our stakeholders have suggested the system must demonstrate the following qualities:

Scalability $($e$.$g$.$ receiving a $50$x traffic boost during large, seasonal sales$)$

Performance $($particularly when customers are searching for products$)$

Affordability $($the business is concerned about over$-$paying for idle compute resources and inefficient database usage$)$

Finally, our technical team has identified the following risks:

Our transactional email processor can have high latency, which can lead to seconds long waits when sending emails

If we don't have visibility into performance and error rates, we won't be able to respond to application issues in a timely manner

Your task is to create a design document for this system which satisfies stakeholder requirements, demonstrates the given desired qualities, and seeks to mitigate the technical risks our team has identified." $[1]$

$1.$ Create a PowerPoint presentation with diagrams showing your architecture and text describing the rationale for your design choices.

$2.$ Post your PowerPoint presentation in this thread.

$3.$ Review all other team presentations and add your comments as a response to their post.