1. Home
  2. Training Library
  3. Architecture (SAA-C02)

Micro Service Design Patterns

The course is part of this learning path

Start course
Overview
Difficulty
Beginner
Duration
1h 53m
Students
31
Ratings
5/5
starstarstarstarstar
Description

Domain One of The AWS Solution Architect Associate exam guide SAA-CO2 requires us to be able to Design a multi-tier architecture solution so that is our topic for this section.
We cover the need to know aspects of how to design Multi-Tier solutions using AWS services. 

Want more? Try a lab playground or do a Lab Challenge!

Learning Objectives

  • Learn some of the essential services for creating multi-tier architect on AWS, including the Simple Queue Service (SQS) and the Simple Notification Service (SNS)
  • Understand data streaming and how Amazon Kinesis can be used to stream data
  • Learn how to design a multi-tier solution on AWS, and the important aspects to take into consideration when doing so
 
Transcript

 Now let's have a look at a full microservices architecture pattern. So let's look at a design pattern that fully utilizes microservices. Now the microservice architecture pattern is not bound by that typical three-tier architecture which we've examined so far. However, that's a popular pattern, and it can realize significant benefits when used with serverless resources. So in our architecture this time, each of the application components are completely decoupled and independently deployed and operated. Amazon API Gateway manages their API, and the functions subsequently are executed by AWS Lambda, and that's all you need to build the microservice. That means your team is free to do other things. 

The challenge with microservice environments is that it does create a few difficulties, like there's repeated overhead for creating each traditional server-designed microservice. We've got to optimize the servers, the density, utilization, et cetera. So when we create microservices using serverless resources, those problems become simpler and easier to solve. The serverless microservice pattern lowers that bar to creation of each subsequent microservice. And optimizing server utilization is not so much of an issue with this pattern. An API gateway provides programmatic-generated client SDKs, which can make it even easier to integrate with other services and other runtimes. Okay, so there's a lot more detail we could go into on both microservice design and serverless design. You don't need to know a lot of granularity for the Solution Architect Associate exam, okay? But this is a very interesting topic. So by all means, once you've passed the exam, come back and learn more about these brilliant architectures.

About the Author
Avatar
Andrew Larkin
Head of Content
Students
109279
Courses
99
Learning Paths
94

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.