Showing Post From Architecture
Self-hosted CI in 2026: revisit Jenkins, Woodpecker CI and Tekton before you add another build agent
Most teams that keep builds on their own servers did not choose their CI engine recently. It was chosen years ago, by someone who may have left, on a machine that has been upgraded “when there was time”.
Read moreServer-side WebAssembly in 2026: revisit Wasmtime, WasmEdge and Wasmer before you run another customer plug-in
Sooner or later, many business products are asked for the same feature: “let our customers write their own rules”. A pricing formula, a validation check, a custom field calculation, a small webhook transformer.
Read moreContainer sandboxing in 2026: revisit gVisor, Kata Containers and Firecracker before you run another untrusted workload
A normal container is a set of Linux processes with namespaces, cgroups, capabilities and a seccomp profile around them. That is a good packaging boundary and a reasonable resource boundary.
Read moreKubernetes backup in 2026: revisit Velero, K8up and Kanister before you trust another cluster restore
Most Kubernetes teams can rebuild a Deployment in two minutes. Fewer can say how long it takes to get back the data that Deployment was using.
Read moreBackground jobs on PostgreSQL in 2026: revisit River, Graphile Worker and Oban before you add Redis just for a job queue
Most web applications need background jobs. Send an SMS after a payment, build a PDF, call a slow partner API, recalculate a report at night.
Read moreDependency updates in 2026: revisit Renovate, Dependabot and Updatecli before another library falls three majors behind
A dependency rarely breaks your system on the day it goes out of date. It breaks it eighteen months later, when a security fix lands only on a major version you skipped, and the upgrade that should have been a ten minute review becomes a two week project.
Read more