- Home
- Training Library
- Serverless, Component Decoupling, and Solution Architectures (SAP-C02)
Design Components - Auto Scaling
Contents
Course Introduction
Utilizing Managed Services and Serverless Architectures to Minimize Cost
Decoupled Architecture
Application services
Amazon API Gateway
Amazon Kinesis
Amazon Elastic Map Reduce
Streaming Data
Mobile Apps
Amazon EventBridge
Design a Multi-Tier Solution
When To Go Serverless
Design considerations
Which services should I use to build a decoupled architecture?
The course is part of this learning path
This section of the AWS Certified Solutions Architect - Professional learning path introduces common AWS solution architectures relevant to the AWS Certified Solutions Architect - Professional exam and the services that support them. These services form a core component of running resilient and performant architectures.
Want more? Try a Lab Playground or do a Lab Challenge!
Learning Objectives
- Learn how to utilize managed services and serverless architectures to minimize cost
- Understand how to use AWS services to process streaming data
- Discover AWS services that support mobile app development
- Understand when to utilize serverless services within your AWS solutions
- Learn which AWS services to use when building a decoupled architecture
Auto Scaling enables horizontal scaling, i.e. adding more instances rather than a vertical scaling, which traditionally tends to be increasing the size or capacity of an instance or machine. When an autoscaling rule is applied, the autoscaling configuration plan launches new instances based on that autoscale configuration. So, autoscaling can be scheduled to scale based on estimated usages, or you can set alarms to scale the size of an autoscale group based on CPU network or memory usage.
So, when any instance in your group reaches a certain threshold, an alarm will be created and the autoscaling group configuration will launch more instances to meet that demand, this is way more resilient. So, if you have a question that mentions high availability, then most likely it is going to need a decoupled multi tier architecture, and it is going to need to be able to scale parts of that application quickly to meet burst activity. So, before we move into design mode, a few questions you need to ask yourself if you're presented with a scenario. Does it need to be highly available?
Does it need to be scalable? Does it need to be fault-tolerant? And in practical terms, does the system need to always be able to answer customer requests? And if so, then it needs to have a multi tier architecture.
Danny has over 20 years of IT experience as a software developer, cloud engineer, and technical trainer. After attending a conference on cloud computing in 2009, he knew he wanted to build his career around what was still a very new, emerging technology at the time — and share this transformational knowledge with others. He has spoken to IT professional audiences at local, regional, and national user groups and conferences. He has delivered in-person classroom and virtual training, interactive webinars, and authored video training courses covering many different technologies, including Amazon Web Services. He currently has six active AWS certifications, including certifications at the Professional and Specialty level.