Operations | Monitoring | ITSM | DevOps | Cloud

The radical shift towards DevOps and the continuous everything movement have changed how organizations develop and deploy software. As the consolidation and standardization of continuous integration and continuous delivery (CI/CD) processes and tools occur in the enterprise, a standardized DevOps model helps organizations deliver faster software functionality at a large scale.

At Honeycomb, we’ve often discussed the value of making software deployments early and often, and being able to understand your code as it runs in production. However, these principles aren’t specific to only your customer-facing software. Configuration-as-code, such as Terraform, is in fact code that needs to go through a release process as well. Lacking formal process around Terraform deployment means a de-facto process that generates reliability risk.

Transformation of IT Ops When I think of the term IT Ops I immediately think of Enterprise IT and the traditional attributes that make up this function – many of which are in the middle of an industry-wide disruption – and its associated impact. At LinkedIn, when we first looked at business process support, shadow IT and non-accounted-for IT spend, about 10 years ago, it was a bit of a revelation to me how the landscape had already changed by then.

I’ve heard many conversations about the limitations of “serverless technology” ever since the concept was widely known. They often focus on how specific implementations of serverless are limited by certain aspects that the user doesn’t have control of. This seems odd to me because serverless isn’t a technology.

The holy grail for any CMO looking for their next gig is to find the perfect combination of addressable market, market timing, company, and product. That’s why I am so excited to be joining the team at Rancher Labs, the leader in container management software. Let’s look at all the variables.

Incidents happen all the time because of bad code deploys. You write some code that passes code review, it then is automatically shipped to production after a test suite passes, and BAM, an outage happens. This fairly common occurrence has ways to prevent it entirely. Using some simple ideas we can defend ourselves from the hidden mistakes that code reviews and chaos engineering sometimes won’t catch.

Now that you’re invited, here’s the lowdown: Starting this Wednesday, you get the unique chance to attend four weeks of live working sessions with some of the top minds in serverless. They’ll prepare you to build production-ready serverless applications with the best practices of AWS top-of-mind. Along the way, you’ll get the chance to earn awesome prizes as you unlock milestones like deploying a stack and finishing your app.