Operations | Monitoring | ITSM | DevOps | Cloud

Annual reports often feel full of fluff, but the 2024 State of Git Collaboration Report, developed by GitKraken in partnership with JetBrains and drawing on insights from 150,000 developers worldwide, gets straight to the heart of what makes the best development teams stand out in 2024.

Many organizations who are looking to introduce Fault Injection as a testing technique start with non-production environments, but don't always go back and reconsider that choice as they mature beyond initial assessment. However, there's a strong case for running these tests in your live systems. It's important to consider the trade-offs when choosing to test in production or non-production environments, as it can have far-reaching impacts on the efficacy and cost of improving the resilience of software.

What does the platform engineering roadmap look like as we head into its continued maturity? We recently conducted a survey to better understand the role and state of platform engineering — emphasizing those organizations who are using this tactic to greater success. Using this data, we will peek into the future and see where platform engineering is headed next.

Today, we are thrilled to announce our brand-new product, “Turbo360”—an ultimate Cloud Management Platform for Microsoft Azure. It’s not a completely new product; we are rebranding and repositioning our successful product Serverless360, to Turbo360 to serve a bigger market and customer base. Serverless360 has evolved into a full-blown cloud management platform in the past seven years.

This week, I met with one of our partners, and my good friend Rik Hepworth asked a great question. This was: “Mike, we really like Azure Documenter in Turbo360, but what would be awesome is if I can generate the documentation from a DevOps pipeline so each time we deploy updates to Azure, we can regenerate the documentation” In this article, we will look at how to do it.

In traditional engineering organizations, development and operations teams are often siloed, a scenario that can lead to friction between them. For example, developers are encouraged to write and release more and better code. Operations engineers are responsible for preventing errors and bugs from affecting customer experiences. As a result, operations teams frequently serve as gatekeepers and can significantly slow deployments down – to ensure everything works first.