Microservices Architectures - Non Functional Requirements - Portability

Image Image

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

What you will learn

  • What Is Portability?
  • Why is Portability important?

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 Portability?

Portability is one of an application’s non-functional requirements.

The question to ask is : What is the cost of migrating or supporting a new platform? What are the costs involved when you need to move to or support a new language, framework , database or cloud provider?

Ideally, you want your application to be as portable as possible, as you don’t want it to be tied to a specific infrastructure.

Let’s say you want to deploy your application to the cloud, and initially choose AWS as your provider. If the application is portable, it would be possible to easily migrate it in the future, to say Google Cloud or Microsoft Azure.

Portability is a trade-off

It is very important to remember that there are costs involved in building portable applications. If we want our application to be deployable to AWS, Azure and GCP - it would limit the architecture choices that are available to you.

  • There might be an awesome AWS feature which you might not be able to leverage

It is always important to analyze the trade-offs and evaluate the costs when it comes to portability.

A Microservices Example

You can assess portability at multiple levels. Consider for example the following diagram of a microservices architecture:

image info

This is an infrastructure where a microservice is deployed. The factors that determine the portability of such a microservice depends on:

  • The language used to develop it
  • The framework employed to develop it
  • The interfaces that are written for it
  • The common components that it makes use of
  • The common infrastructure that it makes use of

Well Defined Interfaces

It is well documented that well-defined interfaces are a major factor in improving an application’s portability. For example, if we write a well-defined interface to talk to the security component, switching to a different security implementation later will be much easier.

Platform Decoupling

The other important point is not to depend in a specific platform feature.

If your application uses a database feature specific to Oracle DB, then it is tied to Oracle DB. If you use a system feature specific to the UNIX OS, then you are again tied to it. If you are using a AWS specific feature, you are tied to AWS.

Avoid platform coupling.

Interacting With Web Services

Another way of improving portability is for the application to have interactions with web services, to consume what they have to offer. This makes sure it is not tied to a particular technology or platform. This is kind of loosely related to the concept of interfaces.

Do check out our video on this:

image info


In this video, we looked at a non-functional requirement called portability. Portability is the cost that is involved in moving an application to a different platform. That could be a new language, framework, or database. We saw that there are multiple levels of portability involved.

Best Selling Udemy Courses

Image Image Image Image Image Image Image Image Image Image

Join 450,000 Learners and 30+ Amazing Courses

350,000 Learners are learning everyday with our Best Selling Courses : Spring Boot 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

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

Understanding jwt token

Let us understand the json web tokens

Single sign-on workflow

Let us understand the single sign-on workflow

Oauth2.0 - Resource Owner Password Credentials grant workflow

Let us understand the Oauth2.0 Resource Owner Password Credentials grant workflow

Oauth2.0 - Implicit grant workflow

Let us understand the Oauth2.0 implicit grant workflow

Oauth2.0 - Client Credentials grant workflow

Let us understand the Oauth2.0 client credentials grant workflow

Oauth2.0 - Authorization grant workflow

Let us understand the Oauth2.0 authorization grant workflow

Writing Integration Tests for Rest Services with Spring Boot

Setting up a basic REST Service with Spring Boot is a cake walk. We will go one step further and add great integration tests!

Integrating Spring Boot and Spring JDBC with H2 and Starter JDBC

Learn using Spring Boot Starter JDBC to connect Spring Boot to H2 (in memory database) using Spring JDBC. You will create a simple project with Spring Boot. You will add code to the project to connect to a database using Spring JDBC. You will learn to implement the basic CRUD methods.

JUnit Tutorial for Beginners in 5 Steps

JUnit Tutorial for Beginners in 5 Steps. Setting up a basic JUnit example and understanding the basics of junit.

JPA and Hibernate Tutorial For Beginners - 10 Steps with Spring Boot and H2

JPA and Hibernate in 10 Steps with H2 - Setting up a basic project example with Spring Boot and in memory database H2. Its a cake walk.