Microservices Architectures - Non Functional Requirements - Availability

In this article, we explore an important non functional requirement called Availability.

What you will learn

  • What Is Availability?
  • Why is Availability important?
  • How can you build more available systems?

Non Functional Requirements and Microservices

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

What Is Availability?

Conceptually, availability is easy to understand. Suppose you wanted to access a website but you found that it is down. That is an indication of low availability of the website.

Availability is a measure of how frequently your system provides the desired functionality, to your users.

Typically, you want a 99.9999% or 100% availability for your system. Actually, this might not be true.

Depending on the category of an application, there might be different needs for its availability. If it is an internal application to be used within an enterprise, then it might not be needed beyond office hours.

For most system that are available over the internet, the availability needs are quite high.

Improving Availability

Consider the following system with a microservices architecture:

image info

How would you go about improving the availability of this system?

Modularity Improves Availability

Microservice architectures have high modularity. We don’t build such a system as a monolith. Instead, we break it down in to smaller components (technical and infrastructure), each of which provides a well defined interface.

Each of them is also independently deployable. Such applications will not be very bulky, nor will they need to access huge databases. That is a good head-start in giving the system high availability, since common bottlenecks are removed.

Redundancy Improves Availability

In the application example above, having multiple instances of each of Microservice1, Microservice2 and Microservice3 helps improve service availability to users.

Not just the microservices, redundancy at other levels is beneficial too. Having multiple instances of the Infrastructure components such as the NamingServer and APIGateway improves availability.

The key to high availability is to eliminate single points of failure. Ensure that all your infrastructure components have enough redundancy built in.

Monitoring Improves Availability

If an API Gateway goes down, you should NOT get to know of it from your users.

If Microservice1 crashes for some reason, you should know of it first through your internal automated mechanisms.

There needs to a facility for monitoring each of the microservices and components in the system.

On any instance of failure, the operations team needs to be alerted by some mechanism, for diagnosis and recovery.

Do check out our video on this:

image info


In this video, we talked about the availability of an application. Availability measures how frequently the system provides the desired service, to all the users. We took the example of a microservice architecture to describe how you can improve availability.

10 Step Reference Courses

Image Image Image Image Image

in28Minutes is helping 300,000 Learners across the world reach their learning goals. Click here for the complete catalogue of 30 Courses.

Related Posts

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.

Spring and Spring Boot Video Tutorials for Beginners

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

Software Design - Separation Of Concerns - with examples

Software architects and programmers love having Seperation of Concerns. What is it? Why is it important? Let's get started.

Object Oriented Software Design - Solid Principles - with examples

Software design is typically complex. Object oriented design takes it to the next level. There are a number of design patterns and other stuff to be aware of. Can we make things simple? What are the goals to aim for when you are doing object oriented design? SOLID Principles is a great starting point for Object Oriented Design.

Software Design - Open Closed Principle - with examples

Open Closed Principle is one of the SOLID Principles. You want your code to be easily extended. How do you achieve it with minimum fuss? Let's get started.

Software Design - What is Dependency Inversion Principle?

Dependency Inversion Principle is one of the important SOLID Principles. Dependency Inversion Principle is implemented by one of the most popular Java frameworks - Spring. What is it all about? How does it help you design good applications?

Introduction to Four Principles Of Simple Design

With agile and extreme programming, the focus is on keeping your design simple. How do you keep your design simple? How do you decide whether your code is good enough?

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.

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?

Designing REST API - What is Code First Approach?

Designing Great REST API is important to have great microservices. Code First approach focuses on generating the contract from code. Is it the best possible approach?