Skip to main content

Scalability Vs Elasticity

SCALABILITY - ability of a system to increase the workload on its current hardware resources (scale up);
ELASTICITY - ability of a system to increase the workload on its current and additional (dynamically added on demand) hardware resources (scale out);


Scalability: "Increasing" the capacity to meet the "increasing" workload.
Elasticity: "Increasing or reducing" the capacity to meet the "increasing or reducing" workload.

Scalability: In a scaling environment, the available resources may exceed to meet the "future demands".
Elasticity: In the elastic environment, the available resources match the "current demands" as closely as possible.

Scalability: Scalability adapts only to the "workload increase" by "provisioning" the resources in an "incremental" manner.
Elasticity: Elasticity adapts to both the "workload increase" as well as "workload decrease" by "provisioning and deprovisioning" resources in an "autonomic" manner.

Scalability: Increasing workload is served with increasing the power of a single computer resource or with increasing the power by a group of computer resources.
Elasticity: Varying workload is served with dynamic variations in the use of computer resources.

Scalability: Scalability enables a corporate to meet expected demands for services with "long-term, strategic needs".
Elasticity: Elasticity enables a corporate to meet unexpected changes in the demand for services with "short-term, tactical needs".

Scalability: It is "increasing" the capacity to serve an environment where workload is increasing.
This scalability could be "Scaling Up" or "Scaling Out".
(Example:
Scaling Up - increasing the ability of an individual server
Scaling out - increasing the ability by adding multiple servers to the individual server.)
Elasticity: It is the ability to "scale up or scale down" the capacity to serve at will.

Scalability: To use a simile, "scaling up" is an individual increasing her power to meet the increasing demands, and "scaling out" is building a team to meet the increasing demands.
Elasticity: To use a simile, a film actor increasing or reducing her body weight to meet differing needs of the film industry.

Comments

Popular posts from this blog

Password reset too simplistic/systematic issue

Some time when we try to reset the password of our user in linux it will show as simple and systematic as below: BAD PASSWORD: it is too simplistic/systematic no matter how hard password you give it will show the same. Solution: ######### Check if your password is Ok with the below command, jino@ndz~$ echo 'D7y8HK#56r89lj&8*&^%&^%#56rlKJ!789l' | cracklib-check D7y8HK#56r89lj&8*&^%&^%#56rlKJ!789l: it is too simplistic/systematic Now Create a password with the below command : jino@ndz~$ echo $(tr -dc '[:graph:]' 7\xi%!W[y*S}g-H7W~gbEB4cv,9:E:K; You can see that this password will be ok with the cracklib-check. jino@ndz~$ echo '7\xi%!W[y*S}g-H7W~gbEB4cv,9:E:K;' | cracklib-check                 7\xi%!W[y*S}g-H7W~gbEB4cv,9:E:K;: OK Thats all, Thanks.

Nginx Ingress controller setup in K8S MultiNode Cluster with HA-Proxy as External LB

https://github.com/nginxinc/kubernetes-ingress/blob/master/docs/installation.md Pre-requisites: ############### >> K8s cluster setup with 1 Master and 2 Worker nodes. >> Deployed an application with Deployment name "client-sb" >> Also you need to create an HA-proxy server by spinning an Ec2 instance. After login the Ha-proxy server. # yum install haproxy # vi /etc/haproxy/haproxy.cfg delete everything after the global and defaults starting from "Main front-end which proxys to the backend" paste the below code in the end of the file: --------------------- frontend http_front   bind *:80   stats uri /haproxy?stats   default_backend http_back backend http_back   balance roundrobin   server kube 10.0.1.14:80   server kube 10.0.1.12:80 --------------------- # systemctl status haproxy # systemctl enable haproxy # systemctl start haproxy 1. Create a Namespace, a SA, the Default Secret, the Customization Confi...

Running K8s cluster service kubelet with Swap Memory Enabled

For enabling swap memory check the below link : https://jinojoseph.blogspot.com/2019/10/enable-swap-memory-using-swapfile-in.html # sudo vi /etc/systemd/system/kubelet.service.d/10-kubeadm.conf Add the KUBELET_EXTRA_ARGS line as below: ---------------------------------------- Environment="KUBELET_EXTRA_ARGS=--fail-swap-on=false" ExecStart= ExecStart=/usr/bin/kubelet $KUBELET_KUBECONFIG_ARGS $KUBELET_CONFIG_ARGS $KUBELET_KUBEADM_ARGS $KUBELET_EXTRA_ARGS Now kubelet.service changed on disk. Run 'systemctl daemon-reload' to reload units # sudo systemctl daemon-reload # sudo systemctl restart kubelet # sudo systemctl status kubelet That is all cheers :p