Category
Sort By
Introduction When you work with AWS infrastructure for some time, you realise that not all problems announce themselves with alerts or outages. Some problems stay quiet, blend into the background, and only reveal themselves later-usually when someone asks a question you can’t answer clearly. This is one such experience from my early...
Introduction DNS is rarely the first thing teams modernise. In most client environments we work with at To The New, CI/CD, cloud infrastructure, and observability mature quickly. DNS, however, often remains manually managed through dashboards, handled by a few people, and changed mostly during incidents. That gap usually goes unnoticed...
Introduction In DevOps, upgrades are rarely exciting. They don’t ship new features (most of the time). They don’t impress clients. They don’t always get leadership applause. And yet, over the years at To The New, one thing has become very clear to us: DevOps teams that do upgrades regularly move faster, stay safer,...
Introduction When teams start on their DevOps journey, the excitement is real. CI/CD pipelines, faster deployments, cloud-native tools, automation everywhere - it feels like everything is finally going to be smooth. But in reality, the first year of DevOps is rarely smooth. It’s messy, experimental, and full of learning. [caption...
Introduction and Usecase There are times when we want Terraform to stop managing a resource, but don’t want to delete it from the infrastructure. In this brief blog, I'm going to discuss removing resources from Terraform configuration files while keeping them in real infrastructure. But why would you want to do this in the first...
Nowadays, every org wants to migrate to a microservices architecture; the idea sounds great on paper. But when you're staring at an 8-year or decade-old monolith that processes millions of transactions and somehow never breaks, suggesting a complete rewrite feels... well, insane. I've been down this road more times than I care to admit....