Operations | Monitoring | ITSM | DevOps | Cloud

As a solutions engineer for FireHydrant, I speak with a wide variety of companies about their incident management programs — from start-ups with a handful of employees to large enterprise companies with thousands of engineers. Whether they’re looking to establish their incident management program or mature it, the same questions remain.

For the last few years, Squadcast has been building out a market-leading on-call and alert management solution. Over the past few quarters, we have significantly enhanced our on-call product by releasing and improving features related to Incident Response - including Slack / MS Teams integration, Runbooks, Postmortems, Service Level Objectives, and Status Pages. We believe that a reliability platform involves both on-call and incident response - one cannot work effectively without the other.

As platform engineering continues to rise in popularity, there is a new side effect to watch out for: the people using the internal developer platforms aren't the people who built it. They’re not necessarily familiar with the codebase, they may not know what's powering it behind the scenes – and the platform might even have to contend with malicious users. So how is Puppet evolving to contend with this new challenge?

How long will you support your device? Long-term support for IoT is a simple but difficult question for many device manufacturers. If you are developing a smart home device, a mobile robot for hospitality, or the next iron man jetpack, you need to consider how long you will support the device on the market. This will have implications on your operational expenses, team resources and customer satisfaction. Simply put, the longer you support your device, the happier your user will be.

Business leaders frequently need to make decisions that could impact the entire future of a company. Armed with pages of data and financial reports, many executives choose to slash costs, double efforts on certain products over others, or otherwise forge ahead with major decisions about cloud usage, spending, and overall business strategy. Great choices could mean huge profits, but unwise choices could spell doom for the business as a whole.

The internet is a network of networks, and how and where those networks interconnect determines the efficacy of the service. How networks exchange traffic on the internet varies. Broadly speaking there are three different approaches: A direct connection via a transit provider, a private interconnection between two networks, or peering at an internet exchange (IX) point - a co-location hub that enables members of the IX to interconnect.

In September, we announced that Steve Wozniak will be joining us at Civo Navigate to discuss his time at Apple and share his thoughts on the future of technology. Grab your tickets for Civo Navigate today! We also hosted the Cloud Native Community meetup in Florida where we had talks from Mark Boost, CEO at Civo, Kunal Kushwaha, Dev Rel Manager at Civo, and a guest speaker from Defense.com speaking about security.

Containers have fast become one of the most efficient ways of virtually deploying applications, offering more agility than a virtual machine (VM) can typically provide. Both containers and VMs are great tools for managing resources and application deployment, but what is the difference between the two, and how do we manage containers?

It's official! After several weeks of development and a summer of Alpha testing, the Qovery V3 is finally in Beta, which means it’s ready for everyone to try here!