DevOps as a Service or an In-house DevOps Team?

DevOps was born because of the desperate need to get the right deployment of the software code by the right people. Earlier, software operators were responsible for deploying and maintaining the code developed by tech developers. However, developers didn’t know the fundamentals of deployment, and operators didn’t know how to move fast while keeping the code stable. Hence, both teams couldn’t work in sync.

Setting the Stage for DevOps

To create a successful DevOps culture, you need support and commitment from both IT and business executives, which can be a challenge to obtain. Many managers, technologists, and business leaders are still not sure what DevOps is, much less why they need it, and the abundance of materials from vendors trying to capitalize on DevOps’ status as something of a buzzword does not help the confusion. As such, education on the benefits of adoption of DevOps core values must be a high priority for anyone looking to lead a digital transformation at their company. Although you’ll be faced with many challenges in this process, the major ones you’re likely to encounter can be boiled down to two generic points: uncertainty about what DevOps is and uncertainty about how it will benefit the organization. In this post, we discuss these challenges, and I provide you with practical strategies for educating stakeholders on how DevOps can optimize business.

Building Modern Applications with AWS

Before we dive in, it's important to level set on what we mean by "modern applications". The good, or perhaps bad, news is that modern practices and modern applications refer to a point in time perspective. What we're going to cover, is based on what modern means, today.