monolithic code bases and creates separate services, or sometimes microservices. This separation creates clearly defined lanes for not only responsibility and accountability, but also for fault isolation. If one service fails, it should only bring down itself and not other services. Pros of Y axis scaling Allows for organizational scale Scales transactions well Fault isolation Increases cache hit rate Cons of Y axis scaling Intellectually hard Takes time to implement Z axis Z axis scaling is usually looking at similar use cases of data. Whether that be geographic in nature or how customers use your website, or even just a random modulus of your customer dataset. The Z Axis breaks customers into sequestered sections to benefit response time and to help eliminate issues if a particular region or section should go down. Pros of Z axis scaling Intellectually easy Scales transactions well Can provide fault isolation Can improve response times Cons of Z axis scaling Takes time to implement Does not address organizational scale Requires increased automation to reduce systems overhead References Computer architecture Computational resources Computer systems Engineering concepts