AWS ELB&ASG

  • Scaling
    • Scaling means that an application/system can handle greater loads by adopting.
    • There are two kinds of scaling
      • Vertical scaling
        • Vertical scalability means increasing the size of the instance.
        • For example, our application runs in T2.micro and we need to increase it to T2.large.
        • Verticals Scalability is very common for non-distributed systems, such as a database.
        • RDS and Elastic cache scale vertically.
        • We can scale vertically by upgrading the instance type.
          • There is usually a limit to how much we can vertical scale, which is the hardware limit.
        • Vertical Scale is increasing, the instance size for EC2 That is scale up or down in instance types
          • From T2.nano 0.5G of Ram and 1vCPU
          • To U-12 TB1.metal-12.3TB of Ram,448 vCPU’s
      • Horizontal scaling also called as elasticity.
        • Horizontal scalability Means increasing the number of instances/systems for your application.
        • Horizontal Scaling implies distributed systems.
        • This is very common for web applications/modern applications.
        • It is easy to horizontally scale with cloud offering such as EC2.
        • Horizontal Scaling is increasing the number of instances that is scale out/in in an EC2 instance.
          • Out is when we increase the number of instances.
          • In is when we decrease the number of instances
          • Used for Auto Scaling groups or Load balancers.
  • Availability
    • High availability goes parallel with horizontal scaling.
    • Higher availability means running your application/system in at least 2 Data centres/availability zones.
    • The goal of high availability is to survive a Data Center loss.
    • High availability can be passive For vertical Scaling(For RDS multi Availability zone, for example)
    • The high availability can be active for horizontal scaling.
    • High availability runs instances for same application across multiple availability zone.
      • Autoscaling Group with multi availability zone enabled.
      • Load Balancer With multi availability zone.

Comments

Post a Comment

Popular posts from this blog

Infrastructure Setup using Cloud Formation Templates

Services Required to create CICD Code Build Build code and deploy image in jfrog Code Pipeline Has (Continuous Integration Continuous Deployment)CICD flow Cloud Formation To deploy and create infrastructure we use yml files. S3 Store our data packages and yml files which are used by CFT. ECS To deploy our application on fargate servers We can also create our manual EC2 instances from pipeline. Secrets Manager Manages all the secrets. ELB/ALB Elastic/Application Load Balancer To map context paths of different services GitHub Stores our code Jfrog Used to store all the docker images Dockerfile Used to create a customised docker image Scanning for Vulnerabilities free code Sonarcube Checkmarx Twistlock Cloudwatch Used to store logs We create log group for each of instances Lambda Functions Used for serverless technologies. Creating a new Environment Create the YML images of the different resources required in the environment. The CFT templates are stored in S3 or can be uploaded from syst...
Read more

VPC,Cloud Front,EC2,RDS in AWS

 VPC allows you to provision a logically isolated section of AWS where we can launch AWS resources in a virtual network. Cloud Front is a Fast Highly Secure and Programmable Content Delivery Network EC2 provides compute resources  RDS is Amazon's Relationship Database System.
Read more

High Availability Architecture

Following points can be considered while creating a highly available architecture depending on scenarios  A spread Placement group Supports a maximum of seven running Instances per availability zone.for example, In A region with three Availability zones, you can run total of 21 instances in the group.If you try to start an eighth Instance in the same availability zone and in the same spread placement group, the Instance will not launch.If you need to have more than seven instances in an availability zone,Then the Recommendation is to use multiple spread Placement Groups. Using multiple spread Placement Groups does not provide guarantee about the spread of instance between groups, but it does ensure the spread for each group, thus limiting impact from certain classes of failures. Durability refers to the ongoing existence of the object or resource. Note that it does not mean you can access it, only that it continues to exist. Groups, Scaling options, configuration templates are comp...
Read more