Showing Post From Operations
Privacy-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 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 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 moreUptime monitoring in 2026: revisit Uptime Kuma, Gatus and the Blackbox Exporter before a customer tells you the site is down
Take a travel company in Udaipur that runs an online booking site for about 140 heritage hotels, lake-side guest houses and homestays in Udaipur, Kumbhalgarh and Mount Abu (an invented example, not a real client).
Read more