The lifecycle of containers — from their high-level orchestration through to their low-level execution in the kernel — requires the interaction of many components, each abstracting away different levels of functionality. In this article we’ll explore the different technologies in this hierarchy which make containers possible. We’ll also touch on virtualization and sandboxing technologies.

Understanding Kubernetes storage is crucial for deployments that rely on persistent volumes within K8s. In this article, we’ll explore various software options for K8s storage based on online research. Additionally, we’ll delve into two specific choices that offer replicated block storage: Piraeus Datastore (LINSTOR) and Rook Ceph.

Behind every Kubernetes network, there’s a crucial component that operates behind the scenes, converting your Services into functional networking rules. This component is known as Kube-Proxy.

In this article, we’ll delve into what Kube-Proxy is, how it functions, and its various modes. We’ll also show you how to inspect IPtables rules for a ClusterIP Service.

In this post, I’ll start off with a brief overview of “shared nothing” vs. “shared storage” architectures in general. This discussion will be a bit abstract and high-level, but the goal is to share with you some of the guiding philosophy that ultimately led to WarpStream’s architecture. We’ll then quickly transition to discussing the trade-offs between the two architectures more specifically in the context of data streaming and WarpStream; this is the WarpStream blog after all!

The Performance Engineering team at GitHub assessed how CPU performance degrades as utilization increases and how this relates to capacity.

Fastmail has a long history of using our own hardware. We have over two decades of experience running and optimising our systems to use our own bare metal servers efficiently.

This article explores the challenges and pitfalls of Terralith, a monolithic Terraform architecture in Infrastructure as Code, and uncovers why a Terralith is not considered best practice.

Terraform users will likely be familiar with “data source will be read during apply” messages that may appear in the plan output. These messages can be confusing and may even lead to unexpected re-creation of resources. Typically, these messages are related to using data sources in combination with Terraform modules and explicit dependencies.

In our company we have thousands of resources managed by Terraform. Which are deployed to multiple environments (dev, staging, production) and different regions.

This go package provides a terminal user interface for ufw.

Techniques to Avoid Potential Failures Caused by Sudden Traffic Spikes

Bento is a high performance and resilient stream processor, able to connect various sources and sinks in a range of brokering patterns and perform hydration, enrichments, transformations and filters on payloads.

A lightweight Database GUI in your browser. It supports connecting to Postgres, MySQL, and SQLite.