Y-axis scaling is based on a functional decomposition of an application into different components. The y-axis of Scale Cube represents the separation of responsibility by role or type of data or work performed by a certain component in a transaction. To split the responsibility, we need to split the components of the system as per their actions or role performed. These roles might be based on large portions of a transaction or a very small one. Based on the size of the role, we can scale these components. This splitting scheme is referred to as a service or resource-oriented splits.
This very much resembles what we see in microservices. We split the entire application based on their roles or actions, and we scale individual ...
