Showing Post From Open Source
Static code analysis in 2026: revisit Semgrep, Opengrep and SonarQube Community Build before you add another code scanner to CI
Most teams add a code scanner to CI in an afternoon. A YAML job, a default rule pack, a green tick.
Read moreSchema registries in 2026: revisit Confluent Schema Registry, Apicurio Registry and Karapace before you ship another event schema
An event schema looks harmless in a pull request. A few fields, a namespace, maybe a default value. But once a producer starts writing with it, that schema is a contract with every consumer that reads the topic today and every consumer that will replay it next year.
Read moreKubernetes storage in 2026: revisit Rook-Ceph, Longhorn and OpenEBS before you put another database on a persistent volume
Running stateless services on Kubernetes is routine now. Running state is where the calm ends. The moment a database or a file store asks for a PersistentVolumeClaim, somebody must answer: where do those bytes live, how many copies exist, and what happens when a node dies at 2 AM?
Read moreRuntime security in 2026: revisit Falco, Tetragon and Tracee before you trust another runtime alert
Most teams now scan images before they ship and check manifests before they reach the cluster. Then the container starts, and for many of us the story stops there.
Read moreReverse proxies in 2026: revisit NGINX, Caddy and HAProxy before you put another proxy in front of your app
Almost every web application we run has something sitting in front of it. A few virtual machines run the actual code, and one or two small servers in front of them accept HTTPS, keep certificates, spread traffic, hide a dead backend and write the access log.
Read moreContainer engines in 2026: revisit Docker Engine, Podman and containerd before you install another container daemon
On most teams, installing a container engine is the first thing done on a new machine and the last thing anybody thinks about.
Read more