Operations | Monitoring | ITSM | DevOps | Cloud

Here at incident.io, we provide a Slack-based incident response tool. The product is powered by a monolithic Go backend service, serving an API that powers Slack interactions, serves an API for our web dashboard, and runs background jobs that help run our customers incidents. Incidents are high-stakes, and we want to know when something has gone wrong. One of the tools we use is Sentry, which is where our Go backend send its errors.

The new world is “always-on,” hyper-connected, massively distributed, and moving at an accelerated “near-real-time” pace.

It’s one of those questions that’s tossed around the internet quite regularly. “Is DevOps dead?” Is there a genuine reason to think that DevOps is on its last legs? Or are authors just trying to get clicks by making controversial statements? Let’s look at some of the main justifications given for raising this question: I’ll come back to these points shortly.

Adopting AWS as your cloud infrastructure seems to be a common choice for most growing companies, but it is not as easy as it looks. Choosing the right services, configuration, and management of these services needs skills and experience. At Qovery, we've heard hundreds of stories about the mistakes made by startups on AWS, and here are the biggest ones. Make sure you take care of these pitfalls when you start your journey on AWS, which will help you successfully migrate and set up on AWS.

When you have more than 150 engineers shipping new features daily, with 8 automatic deployments running at the top of every hour and teams regularly pushing new code, tuning out the noise takes on a whole new meaning. Take monday.com.

When incidents inevitably occur in your software stack, managing them well could be the difference between losing customers and building trust with them. In this article, we’ll give you and your team some best practices on how to prepare for managing incidents. It’s crucial to define service ownership, a declaration process, and practice all of it. With a little planning now, you'll be able to cut your incident response time drastically.