In vertical scaling, we analyze our existing application to find out the parts of the modules that are causing the application to slow down due to higher execution time. Making the code more efficient could be one strategy, so less memory is consumed. This exercise of reducing memory consumption could be for a specific module or the whole application. On the other hand, due to obvious challenges involved in this strategy, instead of changing an application, we could add more resources to our existing IT infrastructure such as upgrading the RAM, adding more disk drives, and so on. Both of these paths in vertical scaling have a limit to how beneficial they are, as after a specific point in time—the resulting benefit would plateau out. It is important here to keep this fact in mind; this kind of scaling requires downtime.