Auto scaling and Metrics Server

Benifits of Autoscaling:

  • High/Improved availability of the application
  • Elasticity
  • Bettter resource utilization
  • Seamless load management  

There are 2 types of Auto scaling 

  • Vertical scaling:  Increasing the capacity of the same single system
  • Horizontal scaling: Increasing number of instances/servers/pods 

In the world of devops, horizontal scaling is best 

HPA: Horizontal POD Autoscaling --> Used to scale up/down no of POD replicas based on observed metris (CPU or memory utilization)

  • It observes all the required metrics, based on that it will add the PODS
  • Tracks multiple metrics, accordingly it will adjust the PODS
  • HPA will interact with Metric server to identify CPU/Memory utilization 

VPA: Vertical POD Autoscaling

Metric server is an application that collects metrics from PODS, nodes according to state of CPU and Memory.  Metric server will not be present by default in the K8S Cluster
The Metrics Server is a scalable, efficient source of container resource metrics for Kubernetes built-in autoscaling pipelines. It collects CPU and memory usage from nodes and pods.

Comments

Post a Comment

Popular posts from this blog

Monolithic Architecture

Image
 Monolithic Architecture In our application, we will have several modules and several components are also available. Components are 1. Presentation Components These are responsible for handling Http Requests. Web applications means front end pages, Distributed applications means Rest Clients. 2. Web Components Responsible to handle user requests.(Servlets basically handles the Requests). 3. Business Components  Responsible to handle the business logic as per the business deals. 4. Persistence Components DAO is responsible for performing DB operations like DML,DDL,TCL,.... 5. Integration Components(Webservices, RestFul Services) Two projects can talk to each other only when we have Integration logic(basically RestfulServices, WebServices,...). 6. Authorization Components Responsible for Authorizing the user. 7. Notification Components Responsible for sending email or mobile message notifications. If we develop all these components as a single project then it is called as " Mono...
Read more

Advantages and Disadvantages of Monolithic Architecture

 Benefits of going for Monolith Architecture  Simple for development(becoz all are available in single project): At initial time it is very easy.   Easy for Testing : End to End Testing we can perform.   Easy for deployment : One war file only we have to deploy to server.   Easy for Scaling : multiple server we can spin easily(horizontal/vertical scaling) if requests increases then we can make keep multiple servers through which the scaling can be done to provide good responses to the client.  Disadvantages of Monolith Architecture  Maintenance of the application: If the application is to large and complex, it is difficult to understand. Change Request in the code is very difficult. Some changes in the existing application will have an impact to the other code, Lot of Impact Analysis will occur.   Adapting to New Technology is required: Change in java version and adapting to the version change also will take time. Applicati...
Read more

Load Balancers and Load Balancers Algorithms

Image
 Load Balancers When all components are in same applications, all request comes to same servers then burden will increase on the same server.  More the requests to the server, then the performance at the server side will be slow so the response time is high for clients.                                                                                                                                  Eg: Youtube, Myntra, Flipkart,.......(lakhs of users will send the request still the response time will be uniform for client)  When burden increased on server it will process the request slowly and some times the server might crash also.  To reduce the bu...
Read more