The downsides of cloud-native solutions

A recent study by Gartner predicts that by 2025 more than 95% of application workloads will exist on cloud-native platforms (up from 30% in 2021). I tend not to believe these kinds of predictions because adoption is never linear. We run out of applications that are easy to convert to new development approaches (in this case, cloud native) and thus adoption slows down or ceases much earlier than most understand.

If you’re still a bit confused by what the heck “cloud native” means, you’re not alone. Here’s my best explanation: 

Cloud-native development is the process of designing, building, and running applications in a cloud computing environment. It leverages the benefits, architectural patterns, and capabilities of the cloud to optimize performance, scalability, and cost efficiency. In other words, we deploy everything to provide cloud-like capabilities, no matter where it runs, cloud and not.

This approach is sold as allowing for faster time to market, increased agility and flexibility, and improved scalability and reliability. It’s a fundamental shift in the way software is developed, deployed, and managed, enabling organizations to take full advantage of the cloud’s capabilities to drive innovation and business growth. Also, it works with popular development tech such as containers and container orchestration.

Cloud-native application development, while offering many benefits, does have its downsides. Most of the people adopting cloud-native approaches and technologies are quick to overlook them. However, they are becoming more apparent as we use the cloud-native approaches to deploy more and more workloads. Keep in mind that I’m not arguing against cloud-native technology, I’m asserting that we need to consider the downsides as well as the upsides. So, here we go.

Vendor lock-in. One of the main issues with cloud-native development and deployment is that it can lead to vendor lock-in. When an application is built and deployed to a specific cloud provider, you typically use the native capabilities of that cloud provider. It can be difficult and costly to move to a different provider or an on-premises platform. This can limit the flexibility of the organization in terms of where they choose to run their applications. It flies in the face of what many believe to be a core capability of cloud-native development: portability.

Copyright © 2023 IDG Communications, Inc.

Source link

Leave a Reply

Your email address will not be published. Required fields are marked *