Microservices Architectures - Non Functional Requirements


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

What you will learn

  • What are non functional requirements?
  • Why are non functional requirements important?
  • What are the different kinds of non functional requirements?
  • How do you ensure that you adhere to non functional requirements?
  • What are the best practices in implementing non functional requirements?

Non Functional Requirements and Microservices

This is the first article in a series of articles on Non Functional Requirements:

What are Non Functional Requirements?

In this article, we focus on the most important non functional requirements and why there are needed.

What Are Non Functional Requirements?

Whenever you talk to a user who needs a web interface, he will mainly describe what needs to happen when the page loads, what it needs to look like, and what should happen when a button on it is clicked. These are the application’s functional requirements.

There is also one other set of requirements that users might not typically specify. For instance:

  • You need to page to load up within 2 seconds (Performance)
  • You require the application to support up to 100,000 concurrent users (Scalability)
  • It should be easy to extend the functionality of the application (Maintainability)

There come under the category of non functional requirements.

As a developer, it is very important that you give due attention to these as well.

Categories Of Non Functional Requirements

Following are some of the important non functional requirements:

  • Authentication & Authorization
  • Performance
  • Scalability
  • Availability
  • Resilience
  • Maintainability
  • Portability
  • Security

Adhering To Best Practices

It is important to adhere to a few best practices, when it comes to implementing the non functional requirements. Here is a list of the most important practices.

  • Have clearly stated non functional requirements
  • Build vertical slices wherever possible, with a view to eliminating non functional risks such as scalability and performance.
  • Make sure that the framework used in your application is able to withstand a particular load.
  • Check for compliance to security requirements right from the project inception stage.
  • Perform static analysis of the code right from project inception.
  • Use Secure Code static analysis tools right from the start of the project.

Do check out our video on this:

image info

Summary

In this article, we discovered what non functional requirements are, and how they are different from the functional requirements. We had a brief look at the types of non functional requirements. Finally, we had a glimpse of the best practices to follow while implementing these requirements.

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?