Be the first to like this
In IT, we sometimes coin terms for things before we know exactly what they are and how they’ll be used. The resulting terms may capture a common set of aspirations and goals—as “cloud” did broadly for on-demand, self-service, and flexible computing. But such a term can also lump together diverse and even competing practices, technologies, and priorities to the point where important distinctions are glossed over and lost.
This is the case with DevOps. On the one hand, many DevOps discussions focus on culture, breaking down silos, making everyone responsible for security, and giving developers operational responsibility for their applications. This is primarily a developer-centric view of DevOps. On the other hand, DevOps (or cloud-native operations if you prefer) can also be approached through the lens of how operations enables developers and relentlessly automates using expert teams--while also managing business risk.
In this session, Red Hat Technology Evangelist Gordon Haff will discuss different patterns for creating next-generation software and provide insight into when particular approaches may be more or less suitable. You’ll leave with a better understanding of optimizing the software delivery pipeline in your organization.