100DaysofCode - Day 02
Hello amazing folks, what an amazing day. The counter is increasing and only 98 day left 
. What I really love about 100daysofcode is the commitment level that increase in me, talking and sharing with my amazing community new topics on a daily basis.
And for today we will start discussing Horizontal scaling / Vertical scaling, how they differ and when to implement each of them.
Horizontal scaling
== Scaling out
-
Horizontal scaling (aka scaling out) refers to adding additional nodes or machines to your infrastructure to cope with new demands.
-
If you are hosting an application on a server and find that it no longer has the capacity or capabilities to handle traffic, adding a server may be your solution.
Advantages ?
-
Increased performance
-
Increased resilience and fault tolerance
-
Scaling is easier from a hardware perspective
-
Fewer periods of downtime
Disadvantages?
-
Increased Initial costs
-
Increased complexity of maintenance and operation - Multiple servers are harder to maintain than a single server is.
Vertical scaling
== Scaling up
-
Coming from the horizontal scaling which means adding new nodes to handle the system traffic, vertical scaling describes adding more power to your current machines. For instance, if your server requires more processing power, vertical scaling would mean upgrading the CPUs. You can also vertically scale the memory, storage, or network speed.
-
Vertical scaling may also describe replacing a server entirely or moving a server’s workload to an upgraded one.
-
Advantages ?
-
Cost-effective
-
Less complex process communication
-
Less complicated maintenance
Disadvantages?
-
Upgrade limitations
-
Single point of failure
-
Higher possibility for downtime