---

#layout: post title: Microservices Architectures - Non Functional Requirements date: 2019-11-14 12:31:19 summary: In this article, we focus on the most important non functional requirements and why there are needed. categories: SwArchitecture permalink: /non-functional-requirements-in-microservices-architectures image: /images/architecture.png

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:

• 1 - Microservices Architectures - Non Functional Requirements{:target='_blank'}
• 2 - Security{:target='_blank'}
• 3 - Web Application Security And OWASP - Top Ten Security Flaws{:target='_blank'}
• 4 - Maintainability{:target='_blank'}
• 5 - Scalability{:target='_blank'}
• 6 - Performance{:target='_blank'}
• 7 - Reusability{:target='_blank'}
• 8 - Reliability{:target='_blank'}
• 9 - Modularity{:target='_blank'}
• 10 - Availability{:target='_blank'}
• 11 - Portability{:target='_blank'}

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:

#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.