Part 1 of 3
According to Microsoft CEO Satya Nadella, “Every business will become a software business, build applications, use advanced analytics and provide SaaS services.” Made at Microsoft’s 2015 Convergence conference, Nadella’s prediction hardly seems far-fetched considering that a modern high-end car features more than 100 million lines of code.
For the last few years, developers have been at the epicenter of a fundamental shift not only in how code is developed, but in where it’s developed. Traditionally, code development has been characterized by periods of requirements accumulation (batching) and justification separated by long periods of coding, testing and integration (only to be followed again by the accumulation and justification of more requirements).
These methods have given way to continuous streams of code development where requirements are addressed in near real time. It’s no longer enough to generate bug-free code. Developers are leading the charge in writing code that can create, store, manage, modify, protect, analyze, and reuse data at a scale that was previously considered unachievable.
Non-iterative development processes have also been replaced. The past “ask-wait-get” interactions, where developers requested resources and authorization to use infrastructure from their operations counterparts, has given way to different service models and ready-to-use development workspaces. The “ask-wait” part of the process has been replaced with only the “get.” IT operations are being bypassed altogether as developers use the cloud as their preferred environment to “get” what they want, when they want it.
DevOps as a practice brings together the development and operations teams. DevOps is not a product or specific solution, nor is it achieved the same way everywhere. It is a way for developers and operations to work together collaboratively and seamlessly. The ultimate objective is to gain a competitive advantage through ever-shrinking application development and deployment timeframes.
In hindsight, this looks like a cultural evolution we should have seen coming rather than a revolutionary shift that was triggered by a major disruption in the application development process.
Stay tuned for the next edition of our three-part series where we’ll look at some major industry trends that have caused this change in how software is developed and how the role of developers and their operations counterparts have become so inextricably linked. We’ll also explore how NetApp, through integration and automation of our data management technologies, plans to bring value to the entire developer workflow.
For more information on DevOps, attend DeveloperWeek 2016. The weeklong tech conference kicks-off February 13th with the DeveloperWeek Hackathon, which will include over $100,000 in cash and prizes. To sign-up for for NetApp’s sponsored challenges at the DeveloperWeek Hackathon, please visit www.netapponcloud.com/hackathon.