What first comes to mind when you hear the term “cloud native”?
Do you think software? Software that was developed in the cloud? Software that didn’t have to be rewritten in order to live happily in a dynamic digital environment?
Fair enough. That’s a natural reaction. A legitimate reaction. And a very nice thought.
But it shouldn’t be your only thought. Because cloud native is a whole lot more than that. It’s the infrastructure sitting beneath all those fun, agile applications. It’s the company culture that gives up a little control in exchange for the massive efficiencies that come with automation and the benefits that result from the freedom to innovate. It’s processes that acknowledge the fact that systems scale better than people.
It’s a lot to think about. And if you’re ready to think about it, I’ve got a treat for you! Today’s podcast guest is none other than the author of Cloud Native Infrastructure—Justin Garrison. This week he sat down to talk with us about:
- Why he wrote the book on Cloud Native Infrastructure
- Which types of organizations should go cloud native—and which shouldn’t
- The importance of culture in succeeding at cloud native
- How to get involved in the open source community
- What to do if you’ve got lots of legacy software and want to move to a more dynamic environment
See the video podcast on our YouTube page, or listen to the audio version on SoundCloud. And if you like what you hear, we invite you to subscribe to our channel so you don’t miss any of the other exciting podcasts we have scheduled over the next several months.
