Operations | Monitoring | ITSM | DevOps | Cloud

Good software development teams are focused on outputs, and can bring key metrics to bear that illustrate just what the engineering organization is building on a daily, monthly and yearly basis. Developer productivity is often assessed retrospectively: if the team is hitting DORA metrics, we assume everything in the lifecycle before production is sound. But the best teams dig deeper, and aim to solve the problem backwards as well as forwards by looking at the process as well as the results.

Kubernetes probes are essential tools for maintaining the health and reliability of applications running in containers. Among these, the liveness probe plays a critical role in checking if an application is running correctly. If it detects any problems, Kubernetes can automatically restart the affected container, thus ensuring the application remains available without manual intervention.

In the fast-paced world of IT, where technologies evolve at lightning speed and the demands on systems and infrastructure are growing exponentially, the temptation to maintain the status quo can be all too enticing. After all, change can be daunting, and the familiar feels safe. What many IT professionals fail to realize, however, is that doing nothing is still a choice – and often, it’s a costly one.

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.