Book Image

AWS Certified Developer - Associate Guide

By : Vipul Tankariya, Bhavin Parmar
Book Image

AWS Certified Developer - Associate Guide

By: Vipul Tankariya, Bhavin Parmar

Overview of this book

AWS Certified Developer - Associate Guide starts with a quick introduction to AWS and the prerequisites to get you started. Then, this book gives you a fair understanding of core AWS services and basic architecture. Next, this book will describe about getting familiar with Identity and Access Management (IAM) along with Virtual private cloud (VPC). Moving ahead you will learn about Elastic Compute cloud (EC2) and handling application traffic with Elastic Load Balancing (ELB). Going ahead you we will talk about Monitoring with CloudWatch, Simple storage service (S3) and Glacier and CloudFront along with other AWS storage options. Next we will take you through AWS DynamoDB – A NoSQL Database Service, Amazon Simple Queue Service (SQS) and CloudFormation Overview. Finally, this book covers understanding Elastic Beanstalk and overview of AWS lambda. At the end of this book, we will cover enough topics, tips and tricks along with mock tests for you to be able to pass the AWS Certified Developer - Associate exam and develop as well as manage your applications on the AWS platform.
Table of Contents (29 chapters)
Title Page
Credits
About the Author
Acknowledgments
About the Author
About the Reviewer
www.PacktPub.com
Customer Feedback
Dedication
Preface
Index

Elasticity versus scalability


Elasticity and scalability are two important characteristics of cloud computing. They describe the way cloud infrastructure is able to expand and shrink to match the actual dynamic workload and are discussed as follows:

  • Scalability: This means adding resources either to the existing instance (scale up) or in parallel to an existing instance (scale out). Scalability is essential to achieve elasticity:
    • Scale up: Changing the instance type from small to large (that is, changing to more memory or compute) is called scaling up. It is also called Vertical Scaling. It may require stopping the existing and running instance. Usually, scaling up is done to get more compute and memory on the same instance. Scaling up is usually suggested for an application that does not support clustering modes easily such as, RDBMS. Usually, scaling up is achieved manually and requires downtime.
    • Scale out: Placing one or more new instances parallel to the existing instance is called scale...