Your company is building a new web$-$based multi$-$tier social media application which is expected to become very popular globally within the next several months.$$ The application will have intensive read and write capabilities at the database layer and will require extensive queries for internal reporting.$$ The application will also contain static content in the form of video and other types of media which the users will access. Although only web content ought to be available to internet users, all instances require access to the internet for updates and patching.

All of the assignments in this course will use the same scenario but will focus on a different objective.

Instructions

Focusing on resiliency $($i$.$e$.,$ maintain an uptime of $99\mathrm{.}99\%$ availability with disaster recovery options$),$ design an initial multi$-$tier application $($with web tier, application tier, and a database tier$)$ using AWS services that will be used by a minimal number of users.$$

Include any caching layers, load balancers, security groups, and any other AWS native services you feel are appropriate.$$

Be sure to consider availability zones, regions, ELBs, EC$2$ instances, storage types, CDNs$,$ caches, etc.$$

Do not worry about application design. Consider only architectural decisions and not whether it will be possible to change the application to do or not do something.

Submission Guidelines

Include a labelled diagram of the architecture showing each layer of the solution.$$

In a written report, describe the concepts outlined in the diagram, referencing the labelled areas.

Describe areas that are relevant but not easily included in a diagram $($e$.$g$.$ identities$).$Describe how each component in the diagram meets the objective of the assignment.$$ Include as much detail as possible.$$Document assumptions when necessary and when design requirements haven$$t been specified.$$

Include at least $3$ references to Module $1$s resources: textbook, readings, videos.