Skip to main content

246 posts tagged with "Engineering"

Engineering insights and technical deep dives

View all tags

PaaS First, Kubernetes Second: The $600K Number Byteiota Got Right (and Wrong)
·Dora Noda·8 min

PaaS First, Kubernetes Second: The $600K Number Byteiota Got Right (and Wrong)

Byteiota's case for defaulting to PaaS over Kubernetes rests on a real $600,000-a-year platform-team number — but that's the cost of hand-building Kubernetes' lifecycle automation, not the cost of Kubernetes itself, and Cluster API v1.12 just automated the biggest line item in it.

self-hosting
PaaS
infrastructure
engineering
+1
Pinterest's MCP Registry Handles 66,000 Monthly Tool Calls: The Architecture Behind It
·Dora Noda·10 min

Pinterest's MCP Registry Handles 66,000 Monthly Tool Calls: The Architecture Behind It

Pinterest's production MCP ecosystem handles 66,000 tool calls a month across Presto, Spark, and Airflow. Here's how its central registry, two-layer auth, and human-in-the-loop gating actually work — and what it means for any platform whose AI-agent tools are about to multiply.

Model Context Protocol
AI agents
self-hosting
PaaS
+1
Podman 6.0 Goes Rootless by Default — And No, It Still Isn't Your Kubelet's Container Runtime
·Dora Noda·8 min

Podman 6.0 Goes Rootless by Default — And No, It Still Isn't Your Kubelet's Container Runtime

Podman 6.0 makes rootless the mandatory default and rips out CNI, slirp4netns, cgroups v1, and BoltDB. Here's what actually changes — and the one thing it doesn't: your Kubernetes nodes still don't run Podman.

self-hosting
PaaS
infrastructure
engineering
Railway's 8-Hour Outage Was a GCP Account Suspension, Not a Railway Bug
·Dora Noda·9 min

Railway's 8-Hour Outage Was a GCP Account Suspension, Not a Railway Bug

Railway ran workloads across GCP, AWS, and its own bare metal — but a single suspended GCP account still took the whole platform down for 8 hours. Here's the exact mechanism, and why owning the machines your control plane runs on is the only real fix.

self-hosting
infrastructure
cloud infrastructure
engineering
+1
Coolify vs Dokploy vs Kubero vs bex: The Single-Box-vs-Fleet Decision
·Dora Noda·10 min

Coolify vs Dokploy vs Kubero vs bex: The Single-Box-vs-Fleet Decision

Coolify, Dokploy, Kubero, and bex all promise git-push deploys you own — but only two of them are actually built to run on a single box, and the other two structurally can't be. Here's the architecture, cost, and failure-mode breakdown that decides which one fits.

self-hosting
PaaS
infrastructure
engineering
+1
CloudNativePG vs Zalando vs StackGres: Why bex Chose CNPG for Managed Postgres
·Dora Noda·8 min

CloudNativePG vs Zalando vs StackGres: Why bex Chose CNPG for Managed Postgres

A concrete, real-decision comparison of the three Kubernetes Postgres operators — CloudNativePG, Zalando, and StackGres — and what self-hosted Supabase's Docker Compose stack still can't match a year after Supabase hired a maintainer to fix it.

self-hosting
PaaS
infrastructure
engineering
The 47-Day Certificate Era: TLS Automation Becomes Mandatory for Self-Hosted Infrastructure
·Dora Noda·8 min

The 47-Day Certificate Era: TLS Automation Becomes Mandatory for Self-Hosted Infrastructure

CA/Browser Forum rules cut TLS certificate lifetimes from 398 to 47 days by 2029, with domain-validation reuse shrinking to 7 hours. Here's the full timeline and what it breaks in self-hosted TLS automation.

security
self-hosting
PaaS
infrastructure
+1
CAPD vs CAPH: One Cluster API, From Your Laptop to Real Hetzner Bare Metal
·Dora Noda·9 min

CAPD vs CAPH: One Cluster API, From Your Laptop to Real Hetzner Bare Metal

CAPD and CAPH speak the exact same Cluster API contract at opposite extremes — one fakes the hardware for local dev, the other provisions real Hetzner dedicated servers. Here's what changes, what doesn't, and the gotchas in between.

self-hosting
PaaS
infrastructure
engineering
Kubernetes Quietly Fixed a Years-Old cgroup v1-to-v2 CPU Priority Bug: What the January 2026 Formula Rewrite Means
·Dora Noda·10 min

Kubernetes Quietly Fixed a Years-Old cgroup v1-to-v2 CPU Priority Bug: What the January 2026 Formula Rewrite Means

A linear formula meant to convert cgroup v1 CPU shares into v2 CPU weight silently gave 1-CPU containers about 39% of the priority they should've had, invisible to kubectl and metrics-server the whole time. Here's the fixed formula, the exact command to audit your own nodes, and what rolling it out across a self-hosted fleet's node images actually requires.

self-hosting
PaaS
infrastructure
engineering
Showing 199–207 of 246 posts
Prev23 / 28Next