The federal government has been told to move to the cloud since Vivek Kundra famously coined the phrase “cloud first” fifteen years ago. Unfortunately, somehow the “how” was not included in the prescription.
In an attempt to achieve assigned goals, we have seen agencies “lift and shift” on premises applications to the cloud. There is the checkbox complete. A simile here is you have a broken-down Fiat in your garage, you move to California and put the broken-down Fiat Spyder in your new west coast garage. Different garage, same malfunctioning automobile.
Why not take advantage of some the unique capabilities the cloud provides in order to leverage this cloud transition?
Today, we sat down with Brandon Hertel, Software Developer for Vidoori. We begin the interview by expanding on some of the flexibility the cloud provides and how a federal agency can use this. The focus of the discussion is coming to terms with the expression “cloud native.”
Brandon argues that “cloud-native” is an approach to software development, we take as an example a federal agency that wants to take an application to the cloud.
We begin the interview by talking about concepts that are part of being cloud native. Brandon Herte. Defines ideas like DevSeOps, Cloud Native Open Standards, micro services, and containers. From his perspective, a federal agency can take an application, move to the cloud, and then include these concepts in order to achieve the goals of scalability, flexibility, and being agile.
This is an interview that gives you a better understanding of some of the concepts of “cloud native.”
Follow John Gilroy on Twitter @RayGilray
Follow John Gilroy on LinkedIn https://www.linkedin.com/in/john-gilroy/
Listen to past episodes of Federal Tech Podcast www.federaltechpodcast.com
