Operations | Monitoring | ITSM | DevOps | Cloud

At Civo we aim to provide users with the tools and knowledge to succeed in the cloud native landscape. So, we’re super excited to announce a brand new tech event, Civo Navigate! Whether you’re looking to join us in person or take part in the event, here’s your guide to all things Civo Navigate.

I remember how excited I was to build my first Network Operations Center (NOC). It was a new idea at the time (yes, I know I’m dating myself), and boy, did we feel like we were cutting edge. The mere idea that we needed a place and a set of tools to monitor our entire infrastructure (because it’s never really been about just the network) was a big transition at the time. How things have changed.

We get it – incidents happen. What differentiates resilient teams from others is how they learn from them: using them as an opportunity to find the biggest improvements in how they work. Incident timelines are one of the most simple and effective tools available to you when it comes to learning from an incident. It’s vital that you ensure they’re accurate and useful, in order to make the biggest improvements after an incident.

Running or operating applications requires several tasks throughout their lifecycle: scaling instances, checking the health, integrating with other applications, running backups, and applying updates – to name a few examples. It’s a time and labour-intensive process. To automate these tasks, developers can implement scripts for repeated execution. This is where the software operator comes in.

Kubernetes is the industry's most popular open-source platform for container orchestration. It helps you automate many tasks related to container management. Companies use it to solve their problems related to deployment, scalability, testing, management, etc. However, Kubernetes is complex and requires a steep learning curve. In this article, we will go through some common Kubernetes pitfalls most companies fall to.

While the cloud offers significant benefits compared to traditional on-premise infrastructure, its inherent elasticity and scalability lead to uncontrolled costs. Cloud costs can be opaque and difficult to analyze — and without some system of identifying the source of costs and how to manage them — they can quickly undermine your profit margins. Since Qovery makes it easy to create on-demand environments, it can drastically grow your cloud costs.

The past ten years marked a significant change in how software teams build and deploy applications. We moved away from bulky, slow, monolithic applications toward lightweight, scalable, distributed service-based applications. Meanwhile, tools like Docker, Kubernetes, and other container platforms helped accelerate this process. Despite this sudden growth, a fundamental question remains: what exactly is a service, and how does it fit into a microservice architecture?