1. Home
  2. Training Library
  3. Amazon Web Services
  4. Courses
  5. Designing Multi-Tier Architectures

Designing Multi-Tier Architectures

play-arrow
Introduction
Overview
DifficultyBeginner
Duration48m
Students1907
Ratings
4.3/5
starstarstarstarstar-half

Description

Domain one of The AWS Solution Architect Associate exam guide requires us to be able to Design a multi-tier architecture solution so that is our topic for this course. 

The objective of this course is to prepare you for answering questions related to this domain. We’ll cover the need to know aspects of how to design Multi-Tier solutions using AWS services.

By the end of this course, you will be well prepared for answering questions related to Domain One in the Solution Architect Associate exam

Architecture basics 
You need to be familiar with a number of technology stacks that are common to multi-tier solution design for the Associate certification- LAMP, MEAN, Serverless and Microservices are relevant patterns to know for the exam. 

What is multi-tier?
A business application generally needs three things. It needs something to interact with users - often called the presentation layer -  it needs something to process those interactions - often called the logic or application layer - and it generally needs somewhere to store the data from that logic and interactions - commonly named as the data tier.

When should you consider multi-tier?
The key thing to remember is that the benefit of multi-tier architecture is that the tiers are decoupled which enables them to be scaled up or down to meet demand. This we generally call burst activity and is a major benefit of building applications in the cloud

When should we consider single-tier?
Single tier generally implies that all your application services are running on the one machine or instance. Single-Tier deployment is generally going to be a cost-effective and easy to manage architecture but speed and cost is about all there is for benefits. Single tier suits development or test environments where finite teams need to work and test quickly. Single tier can also suit very simple applications or small sites with low traffic demand which will benefit from the effective and economical resource utilization single tier allows

So Let’s move into design mode
First we review the design of a multi-tier architecture pattern using instances and load balances.  Then we’ll review how we could create a similar solution using serverless services or a full microservices design. Looking for the types of question material we might get in the exam/ 

AWS Services we use 
The Virtual Private Cloud
Subnets and Availability Zones 
Auto Scaling 
Elastic Load Balancers 
Security groups and NACLs
AWS CloudFront
AWS WAF and AWS Shield 

Serverless Design 
AWS Lambda 
Amazon API Gateway 

Microservices Design 
AWS Secrets Manager 
AWS KMS 

We then review sample questions to apply and solidify our knowledge 

Summary 

 

--

 
 
Andrew Larkin - VP of Content 
Cloudacademy.com
https://www.linkedin.com/in/larky/
ZOOM:https://zoom.us/j/6406373180
Skype: larkytube
+64 27 526 2205
1 Bluxome Street Suite 418, San Francisco, CA 94107 USA.
Swtizerland - Via Penate 16, 6850 Mendrisio (CH) Switzerland.
Read our reviews on G2Crowd & TrustPilot

Transcript

Hello and welcome to designing a Multi-Tier Solution for the AWS Solution Architect Associate exam. My name is Andy Larkin and I'll be your instructor for this course. Domain one of the Solution Architect Associate exam guide requires us to be able to design a multi-tier architecture solution, so that is the topic of this course. My objective is to prepare you for answering questions like the one we see on the screen here. So we'll cover the need to know aspects of how to design Multi-Tier Solutions using AWS services. By the end of this course, you will be well prepared for answering questions related to domain one in the Solution Architect Associate exam guide.

About the Author
Students84341
Courses95
Learning paths52

Head of Content

Andrew is an AWS certified professional who is passionate about helping others learn how to use and gain benefit from AWS technologies. Andrew has worked for AWS and for AWS technology partners Ooyala and Adobe.  His favorite Amazon leadership principle is "Customer Obsession" as everything AWS starts with the customer. Passions around work are cycling and surfing, and having a laugh about the lessons learnt trying to launch two daughters and a few start ups. 

Covered Topics