BACKGROUND IMAGE: iSTOCK/GETTY IMAGES

Guide to practicing cloud-native development

Last updated:July 2017

Editor's note

The software development industry has become replete with talk about taking a DevOps-based approach to building applications that are inherently capable of running on the cloud. Organizations are being told that Agile must be the method, DevOps must be the process and cloud-native development software has to be the end goal. But are vendors pushing too hard on these approaches? Has a drive to encourage best practices deteriorated into a zone of fear mongering? And what exactly does it mean to be cloud-native anyways?

In this essential guide, we will look into exactly what cloud-native development means, along with the benefits and drawbacks to taking a cloud-native approach to development. We will also try to separate the substance from the hype as we examine both the benefits and drawbacks to a DevOps approach to cloud-native software development.

1Cloud-native development fact vs. fiction

Sometimes technology advocates and thought leaders push a little too hard, and that's exactly the case with cloud-native development and the 12-factor app philosophy. Here we take a look at the current hype cycle and try to separate the substance from the superfluous.

2Moving forward with cloud-native DevOps

With a foundational understanding of what DevOps-based cloud-native development is -- and an ability to separate the substance from the hype -- the next step is putting DevOps-based cloud-native development best practices into action.

-ADS BY GOOGLE

SearchCloudApplications

SearchSoftwareQuality

SearchHRSoftware

SearchSAP

SearchERP

DevOpsAgenda

Close