Curious about the Conda universe? Learn what Conda is & where it came from, what Conda packages are, which Conda communities to join, & more!

Containers are one of the most popular ways for businesses to deploy applications. They provide an easy method of packaging applications into self-sufficient units that can be used, moved around, and re-used in any number of ways without breaking the overall functionality of your software. With the possible exception of serverless architecture, containerization is perhaps the best way to achieve smooth, seamless application deployment and minimal hassle with updates and application maintenance.

For those who missed the live conversation, we had a great chat with Nana Janashia around taking the next click in with Kubernetes. As one of the great equalizers between the development and operations teams, Kubernetes has a duality of generics and opinions to power your workloads. This duality can be a complex one to navigate not only dealing with a new paradigm of idempotency and ephemerality but also dealing with a vast amount of choice and seemingly granular.

Many organizations are adopting Kubernetes to gain agility and increased time-to-value. However, complexity, security, and a shortage of IT skills are the top challenges that prevent organizations from effectively deploying Kubernetes. Complexity Kubernetes requires the selection and integration of a host of component services, which makes do-it-yourself (DIY) deployments beyond the scope of most organizations. Kubernetes management also differs significantly from traditional IT environments.

There are many different ways to run a Kubernetes cluster, from setting everything up manually to using a lightweight distribution like K3s. K3s is a Kubernetes distribution built for IoT and edge computing and is excellent for running on low-powered devices like Raspberry Pis. However, you aren’t limited to running it on low-powered hardware; it can be used for anything from a Homelab up to a Production cluster.

When looking for a highly scalable time series database, there are a number of criteria to investigate and evaluate. First up, it’s always a good idea to consider open source software. It’s more likely to have gone through comprehensive troubleshooting, it’s typically more reliable as it has more timely and widespread peer-review, it better guarantees technology independence, it’s easier to find engineers who are familiar with it and it has great security.

Welcome to the second post in a series of “Implementing Microservices on AWS with the Twelve-factor App”. In the first post, we covered the areas around the codebase, configuration, code packaging, code builds, and stateless processes. This article will go through the remaining areas for best practices in microservices. Let’s start the discussion with Port mapping!

Once you have decided to migrate your MySQL database to AWS, choosing the services you need from the lot of options available in AWS can be quite overwhelming. Migrating will inevitably raise the question.

Linux Active Directory (AD) integration is historically one of the most requested functionalities by our corporate users, and with Ubuntu Desktop 22.04, we introduced ADsys, our new Active Directory client. This blog post is part 2 of a series where we will explore the new functionalities in more detail.

What happens when the tools and services you depend on to drive Site Reliability Engineering turn out to be susceptible to reliability failures of their own? That’s the question that teams at about 400 businesses have presumably had to ask themselves this month in the wake of a major outage in Atlassian Cloud.