The latest News and Information on DevOps, CI/CD, Automation and related technologies.
In June, the research firm GigaOm, published the 2022 edition of their annual Radar for AIOps Solutions, having had time to digest the contents, it seems a good time to summarize the key takeaways from the Moogsoft perspective. Firstly, in case you are not familiar with GigaOm, here’s a brief introduction.
APIs are integral to the success of modern enterprises across a wide range of industries, such as finance, logistics, and manufacturing. They not only enable developers to build powerful business solutions by integrating with external applications, but also facilitate communication between internal services. This means that the ability to build reliable, highly-performant APIs—and govern their behavior and performance—is more important than ever.
Delivering business-critical applications and code relies on two key factors; functionality and efficiency. Mock and Unit tests are a few industry standards that aim to ensure the correct functionality of your code, catching potential bugs and issues before deployment. These tests are vital to workflows, CI/CD pipelines, and the overall build and deployment process. While functionality may be sound, one key aspect that is oft-forgotten is the efficiency and performance of your code.
Deep into an incident, Slack firing, up to your ears in decisions, not sure where to turn next? It’s easy for external communication with your customers to fall far down the list of priorities in these moments. However, these are the exact situations where comms are vital, and where underestimating their importance can having damaging and lasting effects on your organisation.
Upgrading your Mattermost server involves a bit of research, preparation, and downtime. The pressure to keep your Mattermost instance healthy and reduce downtime for a core system within your organization can be intimidating. Recently, we worked with a handful of customers who were experiencing issues upgrading from Mattermost v5.37 and v5.39 to v6.x. Unfortunately, migration scripts were required to make significant database changes, and there was an issue in product performance.
When creating an application, developers often rely on many different tools, programs, and people. This collection of agents and actors involved in the software development lifecycle (SDLC) is called the software supply chain. The software supply chain refers to anything that touches or influences applications during development, production, and deployment — including developers, dependencies, network interfaces, and DevOps practices.