# bare-metal Published articles for bare-metal. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## What 143 platform teams told us about keeping infrastructure alive DevFeed: [What 143 platform teams told us about keeping infrastructure alive]() Original publisher: [Read original article]() Author: Oliver Thylmann Published: 2026-09-04T10:15:45Z Content type: opinion Language: en Sources: [Giant Swarm Blog]() Topics: [Platform Engineering](), [Kubernetes](), [cloud-infrastructure](), [Security](), [observability]() Tags: [aws](), [azure](), [bare-metal](), [infrastructure](), [kubernetes](), [observability](), [open-source](), [platform](), [platform-engineering](), [security](), [survey](), [team](), [tech]() ### AI overview Giant Swarm surveyed 143 platform and infrastructure professionals about the ongoing work required to keep production platforms running. The article argues that this platform integration tax is primarily a time cost, with security, reliability, cluster management, and observability consuming engineering capacity. ### Source excerpt The hidden cost of platform engineering isn't building your stack. It's keeping it alive. Giant Swarm surveyed 143 platform teams to find out. ## From Single Instance to Split-Brain: A Database Scaling Journey DevFeed: [From Single Instance to Split-Brain: A Database Scaling Journey]() Original publisher: [Read original article]() Author: Alok Mishra Published: 2026-03-31T18:40:52Z Content type: tutorial Language: en Sources: [Walmart Global Tech]() Topics: [Databases](), [Replication](), [MySQL](), [PostgreSQL](), [Self-hosted](), [backups](), [Cloud](), [Monitoring](), [Amazon EC2](), [Kubernetes]() Tags: [architecture](), [backups](), [bare-metal](), [cloud](), [cloud-services](), [cloud-sql](), [cockroachdb](), [database](), [ec2](), [failover](), [google](), [google-cloud](), [google-cloud-sql](), [kubernetes](), [monitoring](), [mysql](), [postgresql](), [production](), [read-replica](), [recovery](), [software-architecture](), [software-development](), [software-engineering]() ### AI overview This article explains how database scaling commonly uses a single-leader architecture with asynchronous read replicas. It discusses replication lag, stale reads, split-brain risks, read/write traffic separation, and the operational responsibilities of self-managed versus fully managed database services. ### Source excerpt I used to think adding a 'Read Replica' was a magic button for scaling applications. I was wrong. While splitting read and write traffic is a standard system design pattern, implementing it introduces a world of pain - from stale reads to the dreaded Split-Brain problem. Here is how database replication actually works, and how to survive the transition. When people talk about "scaling databases" or "adding read replicas", they are almost always thinking about one specific architecture: Single-leader (Primary-Replica) architecture with asynchronous replication This is the architecture used by: MySQL + replicas PostgreSQL + streaming replication Google Cloud SQL PlanetScale, Neon, Supabase, etc. There is exactly one node that accepts writes -> called the Primary (or Leader/Master). All other nodes are Read Replicas -> they apply changes from the primary as fast as they can, but always with some delay (replication lag). This is the default and dominant model in 99% of applications today. Alternative architectures exist (multi-primary, leaderless, CRDTs, etc.), but they are rare and come with their own very different trade-offs. The second axis that actually matters in practice is: Who manages the replicas and failover for you?1. Self-hosted / Self-managed You run MySQL or PostgreSQL yourself (on EC2, Kubernetes, bare metal, etc.). You are 100% responsible for: Setting up replication Promoting a new primary when the old one dies Routing traffic correctly Handling replication lag Monitoring, backups, point-in-time recovery, etc. 2. Fully-managed cloud services RDS, Aurora, PlanetScale, Neon, Supabase, CockroachDB, Spanner, YugabyteDB, etc. The provider gives you a single connection string (or two: one for writes, one for reads) and magically keeps it pointing to healthy nodes, handles failover in seconds, and often hides (or eliminates) replication lag headaches. This second axis is the one that determines how much pain you will actually feel in production. Now, suppose yo ## Preview: Slice Up Bare-Metal with Slicer DevFeed: [Preview: Slice Up Bare-Metal with Slicer]() Original publisher: [Read original article]() Author: Alex Ellis Published: 2025-08-30T08:09:48Z Content type: release Language: en Sources: [Alex Ellis' Blog]() Topics: [Firecracker](), [Kubernetes](), [OpenFaaS](), [systemd](), [Arch Linux](), [Arm](), [migration](), [Ollama]() Tags: [arm](), [bare-metal](), [boot](), [deploy](), [firecracker](), [k3s](), [kubernetes](), [linux](), [network](), [preview](), [self-hosting](), [slicer](), [storage](), [systemd](), [testing](), [work](), [x86-64]() ### AI overview OpenFaaS Ltd is previewing Slicer, an internal tool that partitions bare-metal hosts into Firecracker microVMs. The article describes use cases including Kubernetes cluster scaling, customer simulations, chaos testing, production troubleshooting, Arm and x86_64 testing, persistent workloads, multi-host deployments, and GPU access for Ollama. ### Source excerpt The easiest and best supported way to learn and deploy Firecracker and microVMs. ## How to run Firecracker without KVM on cloud VMs DevFeed: [How to run Firecracker without KVM on cloud VMs]() Original publisher: [Read original article]() Author: Alex Ellis Published: 2025-02-12T09:05:21Z Content type: tutorial Language: en Sources: [Alex Ellis' Blog]() Topics: [Firecracker](), [virtualization](), [virtual machines](), [Cloud](), [Amazon Web Services](), [Amazon EC2]() Tags: [aws](), [bare-metal](), [cloud](), [ec2](), [firecracker](), [github-actions](), [kvm](), [qemu](), [virtual-machines](), [virtualization]() ### AI overview This tutorial introduces a way to run microVMs on cloud virtual machines without KVM, using the PVM virtualization framework. It explains the limitations of nested virtualization and compares the cost of AWS bare-metal EC2 with alternatives. ### Source excerpt MicroVMs need bare-metal or nested virtualisation with /dev/kvm. But what if that's not available? The PVM virtualisation framework may be the answer. ## Hermès Bélusca-Maïto hired full-time to work on the ReactOS GUI Setup DevFeed: [Hermès Bélusca-Maïto hired full-time to work on the ReactOS GUI Setup]() Original publisher: [Read original article]() Published: 2023-10-01T00:00:00Z Content type: news Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [GUI]() Tags: [bare-metal](), [bootloader](), [community](), [free](), [gui](), [open-source](), [os](), [partition](), [react](), [reactos](), [registry](), [team](), [virtual-machines](), [win32](), [winapi]() ### AI overview ReactOS Deutschland e.V. hired Hermès Bélusca-Maïto to work full-time for five months on the ReactOS GUI Setup. The planned work includes completing setup functionality, adding GPT support, integrating registry callbacks, and making other refinements. ### Source excerpt Our team proudly announces that ReactOS Deutschland e.V. has hired Hermès Bélusca-Maïto to work full-time on the ReactOS GUI Setup for the next 5 months, starting September 2, 2023. Hermès is a long-time contributor and developer who worked on the project since 2012. He has several skills and expertise into various components of ReactOS, notably being the Client/Server Runtime Subsystem (CSRSS), Console Server Subsystem (CONSRV), NTVDM, and others. His upcoming goal is to finish the first-stage ReactOS GUI setup, which offers an alternative to the classic first-stage text-mode setup (also called USETUP). ## First Impressions with the Raspberry Pi 5 DevFeed: [First Impressions with the Raspberry Pi 5]() Original publisher: [Read original article]() Author: Alex Ellis Published: 2023-09-28T10:55:07Z Content type: opinion Language: en Sources: [Alex Ellis' Blog]() Topics: [Raspberry Pi](), [Self-hosted](), [Kubernetes](), [GitHub Actions](), [Firecracker]() Tags: [bare-metal](), [benchmarking](), [raspberrypi](), [servers]() ### AI overview An early, server-focused first-impressions article on the Raspberry Pi 5. The author discusses its PCIe port and potential use for self-hosted servers, Kubernetes clusters, and isolated CI runners. ### Source excerpt For someone who runs the Raspberry Pi as a server, build agent and for Kubernetes, how does the new version stack up? And should you upgrade? ## From Bare Metal to Kubernetes: 6 Ways to Spin DevFeed: [From Bare Metal to Kubernetes: 6 Ways to Spin]() Original publisher: [Read original article]() Author: Matt Butcher Published: 2023-08-08T12:00:00Z Content type: tutorial Language: en Sources: [Fermyon - Experience the next wave of cloud computing.]() Topics: [WebAssembly](), [Serverless](), [Kubernetes](), [Cloud]() Tags: [bare-metal](), [cloud](), [kubernetes](), [serverless](), [webassembly]() ### AI overview The article describes six ways to execute Spin serverless WebAssembly apps, including locally, with Kubernetes, Nomad, and Fermyon Cloud. ### Source excerpt Learn about the many ways you can execute Spin serverless WebAssembly apps - locally, with Kubernetes, Nomad, Fermyon Cloud and more ## Don't Migrate to Kubernetes DevFeed: [Don't Migrate to Kubernetes]() Original publisher: [Read original article]() Author: Mike Delago Published: 2023-04-26T14:23:04Z Content type: opinion Language: en Sources: [Apartment 304]() Topics: [Kubernetes](), [migration](), [Containers](), [Monitoring](), [observability](), [Software Engineering]() Tags: [apartment-304](), [bare-metal](), [ci-cd](), [containerization](), [containers](), [custom-software-solutions](), [devops](), [devops-engineer](), [infrastructure-as-code](), [kubernetes](), [migrate](), [monitoring](), [observability](), [software-architecture](), [software-development](), [software-engineer]() ### AI overview The article argues that organizations should not migrate to Kubernetes directly from bare-metal servers or virtual machines before establishing strong operational practices. It recommends fast infrastructure and configuration changes, efficient testing and deployment, centralized observability and monitoring, and effective container operations before migration. ### Source excerpt Migrating to Kubernetes can be daunting for many organizations. Shifting the goal from "use Kubernetes" to having good operational practices makes for an easier, iterative transition. ## Networking for a Bare-Metal Kubernetes Cluster After AWS DevFeed: [Networking for a Bare-Metal Kubernetes Cluster After AWS]() Original publisher: [Read original article]() Author: ev@goteleport.com (Ev Kontsevoy) Published: 2019-05-14T15:39:34Z Content type: tutorial Language: en Sources: [Teleport]() Topics: [Kubernetes](), [networking](), [Amazon Web Services](), [cloud-infrastructure](), [Containers](), [Software-defined networking]() Tags: [aws](), [bare-metal](), [hardware](), [ip](), [k8s](), [kubernetes](), [lan](), [networking](), [router](), [sdn]() ### AI overview This article explains how to design a simple, non-redundant network for a small bare-metal Kubernetes environment in a colocation facility after leaving AWS. It discusses network complexity, legacy limitations, SDN concepts, public subnet routing, and separate private LANs for management, security, and performance. ### Source excerpt This is part three of a three-part series on considerations that companies will want to address if they decide to build their own cloud environment. ## RISC-V unikernels and open firmware at QCon and Open Compute Summit DevFeed: [RISC-V unikernels and open firmware at QCon and Open Compute Summit]() Original publisher: [Read original article]() Published: 2019-03-17T15:25:24Z Content type: opinion Language: en Sources: [Jessie Frazelle]() Topics: [RISC-V](), [Open Source](), [Hardware](), [coreboot]() Tags: [bare-metal](), [cloud](), [coreboot](), [hardware](), [open-source](), [risc-v]() ### AI overview The author reflects on discussions about RISC-V support in major cloud providers, MirageOS unikernels booting on bare-metal RISC-V, and open firmware demonstrations using LinuxBoot and Coreboot at the Open Compute Summit. ### Source excerpt I have written a bit about how I am spending my time while being unemployed and I thought I would continue. There was one thing I had left out of my previous post on my visit to the Pentagon. THEY HAVE A REAL ENIGMA MACHINE THERE. Okay, moving on... QCon and University of Cambridge I gave a talk at QCon on SGX and ended up giving the same talk to some really awesome folks at University of Cambridge. Each time I gave the talk provoked some really interesting conversations. One of the topics that came up a couple of times was if RISC-V was going to be supported by any major cloud provider anytime soon. My honest opinion, which some might disagree with, is this is years away BUT it would certainly help adoption and integration into projects if it was backed by a company with a lot of time to develop integrations. Also I got a bit nerd sniped by some ARM folks and researchers to look more into TrustZone (which is the ARM secure enclave). I haven't dug in yet but it's on my list. It was awesome spending a day in Cambridge (thanks Anil for the tour!) and learning about all the awesome things they are doing. The MirageOS team is booting unikernels on baremetal RISC-V! 🎉OCaml boots on bare-metal @ShaktiProcessor @risc_v! 🎉 An important milestone towards building safer apps using @OpenMirage on open source hardware. pic.twitter.com/XFosAxPROR -- KC Sivaramakrishnan (@kc_srk) March 1, 2019 They use this on boards to power light bulbs (at the University!) super securely since it removes the need for all the shitty firmware most other things ship and has a super minimal environment. I'm sure you can think of a number of different other use cases as well. Honestly, unikernels replacing all the crap firmware in the world would be a huge win. Open Compute Summit Just this past week I spent a day at the Open Compute Summit. What is happening there in the open firmware space is truly awesome. They had demos of hardware they are booting with LinuxBoot and Coreboot. Facebook runs this on ## Monitoring Kubernetes in Production DevFeed: [Monitoring Kubernetes in Production]() Original publisher: [Read original article]() Author: info@goteleport.com (Dmitry Shelenin) Published: 2016-03-12T00:00:00Z Content type: tutorial Language: en Sources: [Teleport]() Topics: [Kubernetes](), [Monitoring](), [Kubernetes clusters](), [Latency](), [upgrade](), [Amazon Web Services](), [Linux](), [Docker]() Tags: [amazon-web-services-aws](), [bare-metal](), [docker](), [kubernetes](), [kubernetes-clusters](), [latency](), [linux](), [logs](), [monitoring](), [network](), [production](), [upgrade]() ### AI overview This article explains how to monitor Kubernetes itself in production, especially after upgrades, rather than only monitoring applications. It describes failures involving SkyDNS, etcd, network-attached disk latency, connectivity, nodes, the API server, and Docker across AWS and bare-metal Linux deployments. ### Source excerpt Kubernetes has great built-in application monitoring features. But how to make sure Kubernetes itself is healthy after you upgrade it to the next version? ## Bare Metal Big Data Builds DevFeed: [Bare Metal Big Data Builds]() Original publisher: [Read original article]() Author: Target Brands, Inc Published: 2016-01-13T06:00:00Z Content type: article Language: en Sources: [Target]() Topics: [Hadoop](), [Automation](), [openstack](), [Nova](), [Jenkins](), [Bash](), [Python](), [API]() Tags: [ambari](), [api](), [automation](), [bare-metal](), [bash](), [big-data](), [chef](), [hadoop](), [infrastructure](), [ironic](), [jenkins](), [nova](), [openstack](), [python]() ### AI overview This engineering article describes Target's transition from manually building on-premise Hadoop clusters to an automated bare-metal provisioning workflow. It combines OpenStack Ironic and the Nova client with user-data bash scripts and Chef cookbooks to bootstrap servers, configure node roles, and add them to clusters. ### Source excerpt When you first think about scaling an on-premise Hadoop cluster your mind jumps to the process and the teams involved in building the servers, the time needed for configuring them and then the stability required while getting them into the cluster. Here at Target that process used to be measured in months. The story below outlines our journey around scaling our Hadoop cluster, taking the months to hours and adding hundreds of servers in a couple weeks. The Need Early 2013 taught us the lesson that manually managing Hadoop clusters, no matter how small is a time consuming and very repetitive task. Our next cluster build in 2014 drove the adoption of Chef, Artifactory and Jenkins to help with cluster operations. We stood up those components and created new role cookbooks to manage everything on the OS (configurations, storage, Kerberos, MySQL, etc.). While this was a step in the right direction, it left us with a manual process to still create the initial base server build and then add it to the cluster after configuring it with Chef. Build Foundation Closing the gap in our automation meant finding a way to deliver on true end to end builds, from an initial bootstrap to running jobs in your cluster. OpenStack's Ironic project was the first piece of the puzzle. Ironic gives us the ability to provision bare metal servers, similar to how OpenStack automated the VM build process. With Ironic as the foundation, we leveraged the Nova client to manage our instance builds. The nova python client interacts with the Compute service's API, giving us an easy way to specify our build parameters and spinning up an instance on one of our physical servers. The other key piece with the nova client is the ability to send boot information to the server using user data. The bash script sent executes several commands to install the Chef client, setup public keys and run the initial knife bootstrap to set the run list for the build. Example nova boot command: nova boot --image $image_name ## iOS Build Infrastructure DevFeed: [iOS Build Infrastructure]() Original publisher: [Read original article]() Author: Square Engineering Published: 2015-07-28T16:09:00Z Content type: article Language: en Sources: [Square Corner Blog RSS Feed]() Topics: [iOS](), [ci](), [Jenkins](), [Testing](), [virtualization](), [Intel Core](), [systems]() Tags: [bare-metal](), [ci](), [continuous-integration](), [engineering](), [hdmi](), [infrastructure](), [intel-core](), [ios](), [jenkins](), [mac](), [optimization](), [pcie](), [performance](), [simulator](), [testing]() ### AI overview Square describes the backend infrastructure for its iOS continuous integration and testing cluster. The setup uses Jenkins, a custom Stash plugin, and bare-metal Mac build slaves because virtualization performed poorly for the workload. The selected hardware and fake HDMI monitors improved test performance and enabled the cluster to scale beyond eight machines. ### Source excerpt How we configured our Mac minis to run builds