Showing Post From Architecture
Configuration management in 2026: revisit Ansible, Salt and Puppet before you write another server setup script
Almost every team has one: a setup.sh or bootstrap.sh written for the first production server and grown every year since. It installs packages, edits configuration files with sed, creates users and starts services.
Read morePrivacy-friendly web analytics in 2026: revisit Matomo, Plausible and Umami before you add another tracking script
Most teams do not choose their web analytics. Someone pastes a Google tag into the site header during launch week, marketing adds Google Tag Manager a few months later, and after that the analytics setup grows by one script at a time.
Read moreMySQL-compatible databases in 2026: revisit MySQL, MariaDB and Percona Server before you upgrade another database
Most teams that run MySQL do not choose their database every year. They chose it once, long ago, and since then they have only upgraded it, or not upgraded it.
Read morePython dependency tooling in 2026: revisit pip, Poetry and uv before you rebuild another virtualenv
Every Python team has the same conversation at least once a year. One developer has started using uv on a side project and wants to move every service to it, because installs that took a minute now take a few seconds.
Read moreKubernetes packaging in 2026: revisit Helm, Kustomize and Timoni before you template another YAML file
Sooner or later every team on Kubernetes has the same argument. One person says Helm charts have become unreadable and the team should move to plain YAML with Kustomize overlays.
Read moreServer-side JavaScript runtimes in 2026: revisit Node.js, Deno and Bun before you move another service off Node.js
Every few months someone in a JavaScript team asks the same question: should we move this service to Bun, or to Deno?
Read more