A simple and high-level design is fine, and you can base much of it off a reference model- just don’t copy one directly!

This assignment will require you to identify the components of a cloud solution, and how they relate and integrate with each other.

The work must be your own, but you are allowed to base much of your solution on the AWS reference architecture shared this week in the module. However, do not cut-and-paste any content. If you do not have a drawing tool like Visio, you can download any free drawing tool or create your architecture with a pencil and paper.

Details:

The assignment includes creating a cloud architecture diagram with an explanation, similar to the AWS reference architecture example I shared with the class.

Use the following template:

1. Purpose of the diagram: What transaction is being described.

2. Cloud architecture diagram.

3. Description of the transaction, with each numbered step explained and with each step number matching an arrow number in your diagram.

4. Logical (non-vendor functional labels) Definitions of each diagram component. (i.e. Web Server, etc.)

You should include:

1. A clear overview of the type of business transaction(s) supported by your architecture model (diagram), and a specific transaction example, not a generic transaction type. For example, “This model runs an online clothing store supporting purchases and returns. In this example the business transaction is a customer is buying a pair of running shoes.”

2. Your cloud solution architecture diagram, with a clear boundary line showing what is included inside vs. outside the cloud.

3. Definitions for each of the objects and arrows in your diagram.

The objects should include, at minimum:

End User
End User Access Channel (phone, tablet, PC, etc.)
Cloud Boundary
Load Balancers
Web Servers
Applications
Databases
Numbered One-way Arrows (showing the transaction flow, and the return message to the end user)
4. An explanation of how a specific transaction would flow through your model (such as buying a pair of shoes from an online merchant), from the very beginning through to a confirmation message to the end user reporting a successful outcome. This is best accomplished by numbering each of the one-way arrows and walking through the transaction step-by-step, noting the way your diagram supports each step. Please use green arrows for outbound transaction flows (typically from the end-user onward), and red arrows for the return flow (typically from the database servers back through the model.)

5. You can hand-draw your diagram, or use Visio or another drawing tool. An example of a good, free architecture drawing tool can be found at www.cloudskew.com

The assignment for this week is worth 100 points. Each of the following criteria will be weighted equally in the assessment of this assignment:

1. Included all required cloud components,

2. Defined all of the components and explained their purpose,

3. Represented the components? relationships to each other, and

4. Explained how your architecture diagram supports the specific business transaction

5. Detailed each step of the business transaction (such as buying a pair of shoes), with each step mapping to a numbered, one-way arrow.

Writing assignments are submitted through the TurnItIn plagiarism tool, which evaluates and assigns a score for originality. If you receive a score greater than 20%, you will need to rework your paper before submitting. You are responsible for reviewing this prior to submitting your work.

Please don’t overthink this cloud architecture assignment. You can heavily use the AWS reference architecture diagram for your solution. Please ensure a transaction is clearly described, step-by-step, as it moves through your diagram to be completed.

AWS does not appear to provide this reference architecture currently, possibly due to more advanced approaches shown instead. It is still a great starting point, and it’s important to be familiar with the core components included. The following videos present the reference model content. Please note, there may be additional small components included in these videos as they are more recent than the reference model.

4/2/22, 6:45 PM DocViewer

ZOOM

https://georgetown.instructure.com/courses/151411/pages/module-3-overview?module_item_id=2650223 1/1