Microservices Architectures - Non Functional Requirements - Scalability


350,000 Learners are learning everyday with our Best Selling Courses : Microservices, Spring, Spring Boot, Web Services, Hibernate, Full Stack React, Full Stack Angular, Python, Spring Interview Guide, Java Interview, Java Functional Programming, AWS, Docker, Kubernetes, PCF, AWS Fargate and Azure

In this article, we explore the important non functional requirement called Scalability.

What you will learn

  • What Is Scalability?
  • Why is Scalability important?
  • What are the different types of Scalability?
  • What are the best practices in building Scalable systems?

Free Courses - Learn in 10 Steps

Non Functional Requirements and Microservices

This is the part of a series of articles on Non Functional Requirements:

What Is Scalabiity?

Let’s say we have an application A, that supports N number of users with its current infrastructure.

If we increase the infrastructure by a factor of 10, can we hope to support 10 times the current users?

This is at the heart of scalability.

How we can we support a multifold increase in number of users with a linear increase in infrastructure?

The question that naturally follows is

  • How do you build scalable applications?

For that, we need to understand the types of scalability.

Types Of Scalability

At a high level, there are two kinds of scalability:

  • Vertical
  • Horizontal

What Is Vertical Scalability?

Vertical scalability is all about increasing the hardware and processing capacity available to a system.

Consider the following microservice architecture:

image info

Suppose Microservice1 is deployed on a specific system. Vertical scaling for Microservice1 system would be achieved by increasing the CPU processing power, or by augmenting the amount of main memory on the physical server.

Vertical scalability has limits - Its very expensive to purchase powerful hardware. Vertical Scalability can only help you to a certain extent.

What Is Horizontal Scalability?

How about having 5 instances of Microservice1 instead of just 1 instance? How about having 5 Naming Servers and 2 API Gateways? This is the core thought process for Horizontal Scalability.

Most of the times that we talk of scalability, we refer to horizontal scalability.

Discussing horizontal scalability brings us to a very important question: “How do you build scalable applications?”

Building Scalable Applications

Let’s look at few of the important factors to consider when building an application which can scale.

Have Modular Applications

A very important factor in scalable applications is modularity of your applications. In our example microservice architecture, there are multiple modules or components, each of which can be independently deployed. For example, you can increase the number of instances of each of the microservices, independently.

If you have large monolith applications, or large monolith databases with huge amounts of data within them, they become huge bottlenecks. For example, it is very hard to replicate large databases, or to scale them, vertically or horizontally. Same is the case with monolith applications.

An important step in improving scalability is to make the application more modular, by adopting a microservice architecture, for example.

Improve Caching

If part of the system has higher load, and we access certain data very frequently, caching is a viable option to improve scalability.

Enterprise web applications generally have a lot of data available that can be cached. Microservice3 from our example above might be returning the list of all states for a particular user request. To improve efficiency for future requests, Microservice1 can cache this result, once a day. That can potentially reduce the load on Microservice3.

Another option would be to have a built-in cache for each of the microservices. For example, Microservice1 need not connect to a database to get results for a query; it can use an internal cache.

A distributed cache caching data across different instances of a microservice might also be an option.

Do check out our video on this:

image info

Summary

In this article, we introduced you to the concept of scalability. Scalability addresses the aspect of addressing increased load with minimal increase in system infrastructure.

We saw that there are two main kinds of scalability: vertical and horizontal.

Scalalbility of an application can be improved by designing it in a more modular manner. Different kinds of caches can also help with Scalability.

What to Learn Next?

350,000 Learners are learning everyday with our Best Selling Courses : Microservices, Spring, Spring Boot, Web Services, Hibernate, Full Stack React, Full Stack Angular, Python, Spring Interview Guide, Java Interview, Java Functional Programming, AWS, Docker, Kubernetes, PCF, AWS Fargate and Azure


85,000 Subscribers are learning from our Free Videos on YouTube : JSP Servlets, Spring, Spring Boot, Spring MVC, Hibernate, Eclipse, Maven, JUnit, Mockito, Full Stack - React, Full Stack - Angular, Docker, Kubernetes, AWS, AWS Fargate, PCF and Azure


Here are the recommend articles to read next : Spring Interview Questions, Spring Boot Interview Questions, Microservices, Hibernate, Spring Security, REST API with Spring Boot, Full Stack with React, SOAP Web Services, Exception Handling, Embedded Servers, Spring Data Rest, Spring vs Spring MVC vs Spring Boot, Building Web Application and Spring Data JPA. You can checkout all our 100+ articles here - All Articles.


Do not know where to start your learning journey? Check out our amazing learning paths: Learning Path 01 - Spring and Spring Boot Web Applications and API Developer, Learning Path 02 - Full Stack Developer with Spring Boot, React & Angular, Learning Path 03 - Cloud Microservices Developer with Docker and Kubernetes, Learning Path 04 - Learn Cloud with Spring Boot, AWS, Azure and PCF and Learning Path 05 - Learn AWS with Microservices, Docker and Kubernetes


Related Posts

Deploy Java Spring Boot Applications to AWS, Azure, GCP with Docker and Kubernetes

In this article, we focus our attention on the cloud. How to learn the cloud and deploy Java Spring Boot Applications to AWS, Azure, GCP with Docker and Kubernetes?

Software Design - Single Responsibility Principle - with examples

For me, Single Responsibility Principle is the most important design principle. What is Single Responsibility Principle? How do you use it? How does it help with making your software better? Let's get started.

Spring Boot Tutorials for Beginners

At in28Minutes, we are creating a number of tutorials with videos, articles & courses on Spring Boot for Beginners and Experienced Developers. This resources will help you learn and gain expertise at Spring Boot.

Microservices with Spring Boot and Java - Part 1 - Getting Started

Let's learn the basics of microservices and microservices architectures. We will also start looking at a basic implementation of a microservice with Spring Boot. We will create a couple of microservices and get them to talk to each other using Eureka Naming Server and Ribbon for Client Side Load Balancing. In part 1 of this series, lets get introduced to the concept of microservices and understand how to create great microservices with Spring Boot and Spring Cloud.

20+ Spring Boot Projects with Code Examples

At in28Minutes, we have created more than 20 projects with code examples on Github. We have 50+ articles explaining these projects. These code examples will you learn and gain expertise at Spring Boot.

REST API Best Practices - With Design Examples from Java and Spring Web Services

Designing Great REST API is important to have great microservices. How do you design your REST API? What are the best practices?

Index - 500+ Videos

At in28Minutes, we are creating a number of tutorials with videos, articles & courses on Spring Boot for Beginners and Experienced Developers. Here's a list of video tutorials and courses for you

Creating Spring Boot and React Java Full Stack Application with Maven

This guide helps you create a Java full stack application with all the CRUD (Create, Read, Update and Delete) features using React as Frontend framework and Spring Boot as the backend REST API. We use Maven as the build tool.

Creating a SOAP Web Service with Spring Boot Starter Web Services

Let's learn how to create a SOAP Web Service with Spring Boot Starter Web Services. We will take a Contract First approach by definining an XSD and exposing a WSDL from it.