We have made much of why we went with Rancher’s k3s to underpin Civo’s managed Kubernetes service in posts such as Andy’s explanation of k8s vs k3s, but I wanted to take a bit of a deeper dive into k3s and why in particular it is a great technological choice for a service such as ours.

Some of the most common challenges we hear about from customers are things that might be all too familiar to some of you. Things in IT have always changed rapidly, and it’s only picking up speed. The explosion of DevOps, cloud-centric architectures, and software-defined networking are making it increasingly difficult to keep monitoring and management tools in sync with the environment. This leads to another issue – management and individual teams lack visibility into the whole environment.

You might be on the move. You might be breaking into the field. You might be trying to level up with your next gig. You might be ready for a manager’s role. Regardless of the reason, you are wondering what you need to re-study for your job interviews and “homework” assignments. Even with years of experience, every new gig expects you to answer different kinds of DevOps interview questions.

The promise of Cloudsmith is simple. We ensure development teams have access to the packages they need, when they need them. And we do that through a private, cloud-based repository that can help shield the business from malware, security and licensing concerns related to the use of third party software packages, whilst giving you total control over access to your own packages.

This post by Manca Bizjak of XLAB Steampunk was originally published on the Ansible blog. In Getting Started With Ansible Content Collections, which presented the general idea behind what is becoming a new standard in the distribution of Ansible content, we learned about the what, the why and the how of Ansible Collections (and hopefully it got you excited about Ansible Collections!).

Looking back over 2019 it's been a huge time of change for us as a company. When I co-founded Civo four years ago we were aiming to be an IaaS (Infrastructure-As-A-Service) provider, focusing on small developers and teams rather than huge corporate hosting requirements. The developer experience was really important to us, but trying to carve out a niche in such a crowded market was really challenging.

January 30, 2020 As a healthcare CIO mandated with the transition to electronic healthcare records, you’ve done your due diligence, evaluated various EHR vendors and most likely settled on Epic, a software vendor with over 25% of the US acute care hospital market share. You’ve followed Epic guidelines for minimum hardware requirements and acquired what you believe is the right workstation, server, networking, and storage infrastructure for Epic.

Making sure you don't overspend on AWS is a perennial challenge for many software companies. To help make sure you don't surpass your budget, AWS offers billing alerts, which send you an alert when your costs have reached a certain threshold. This can be a handy way to keep your costs in check, but can take some time to set up and will cost you some extra money.