Cloud native can not be bought or downloaded, it’s a methodology that applies to infrastructure and software. By adopting cloud native practices in software development, testing and production are accelerated which in turn adds value to the business faster.
We invited Chris O'Malley, Senior Practice Manager, Nate Michael, Practice Manager and Matt Puccio, Practice Manager, from the Cloud Native Development group at Rackspace Technology to the Cloud Talk podcast. They chatted with technology evangelist and host Jeff DeVerter to explore the benefits of a cloud native methodology.
Tune in to hear the following:
How to overcome the challenges of adopting a cloud native approach
The benefits of cloud native including automation, scaling and security
The impact of cloud native on traditional IT roles
How to get started with a cloud native approach
Chris O'Malley explains how a cloud native methodology benefits a business. “A cloud native approach, along with tools and rethinking your architecture can unlock the ability to release more frequently. And that's part of the idea of adding business value. We're not just releasing hot new features monthly, like we used to, but we're able to do this much more frequently, to test, and to see how our customers are going to react to things quickly.”
Nate Michael echoes and expands by saying. “You’re looking at efficient smaller teams which are cost-effective. You're able to iterate much faster and try things. You can find out what works and what doesn't work, faster. You can just keep moving, instead of getting bogged down. And it helps avoid technical debt as time goes on.”
Adopting these processes also requires a change in mindset as Nate shares. “From tip to tail, it really is a shift in thinking, especially from a traditional software development approach. I would say, a lot of the processes have to change and bend and adapt to this new way of thinking. It doesn't have to be wholesale, you can do it in phases gradually.”
Matt Puccio reveals a cloud native approach enables security to be built into tooling and infrastructure. “We can automatically scan for vulnerabilities in code bases and across cloud provider accounts. We can do dynamic code testing and static analysis. And technology companies have integrations that we can incorporate in our build processes.
“We can keep scaling to see what account structures look like. Because ultimately, networks are running in accounts and people need access up to user management. We're really focusing on security tooling beyond just code applications and our deployments.”
When it comes to taking the first steps to a cloud native approach many businesses are hesitant. “Avoid paralysis by analysis. There’s many decisions to make, ranging from hiring people down to specific build tools,” says Matt. “Set a small goal and keep iterating on those goals. Make your decisions for what your business needs now and make the decisions for what your business needs in a year, in a year’s time. There's no reason to make all of those decisions upfront.”
About the Authors
Rackspace Technology Staff - Solve
The Solve team is made up of a curator team, an editorial team and various technology experts as contributors. The curator team: Eric Miller, CTO, Rackspace Technology Jeff DeVerter, Chief Technology Evangelist, Rackspace Technology The editorial team: Gracie LePere, Program Manager Chris Schwartz, Editor & Producer Larry Meyer, Creative Management Royce Stewart, Chief Designer Simon Andolina, Design Tim Mann, Design Lisa Varrall, Design Abi Watson, Design Debbie Talley, Production Manager Chris Barlow, Editor Kamalpreet Badasha, Writer Tim Hennessey Jr., Writer Craig Grannell, Writer Karen Taylor, Writer Brooke Kaczmarek, Social Media ManagerRead more about Rackspace Technology Staff - Solve