GitOps-First Internal Developer Platform
A platform engineering case study that eliminated infrastructure wait times and standardised delivery across engineering teams through a self-service, GitOps-driven developer platform.
A platform engineering case study that eliminated infrastructure wait times and standardised delivery across engineering teams through a self-service, GitOps-driven developer platform.
A cloud migration case study that moved containerised workloads from Azure to AWS with zero downtime, driven by a post-merger consolidation requirement.
Its not mandatory but its essential Intro A service mesh is an infrastructure layer that manages how services talk to each other inside Kubernetes. It matters because as applications grow into many microservices, communication becomes harder to secure, monitor, and control. The Core Problem in Kubernetes Kubernetes handles deployment, scaling, and networking. But it doesn’t
REST was never meant to be exciting. It was meant to be boring, predictable, and reliable. That is why it stuck around. Most teams start with REST. – Clear endpoints. – Familiar HTTP semantics. – Caching that works without much effort. Then the product grows. – Clients want different shapes of data. – Endpoints multiply.
No magic tricks. Just small, boring decisions that compound faster than you expect. A while ago, I looked at one of my Docker images and paused. 2.3 GB. For a service that barely did anything. You know Docker. You know the best practices. You have read the blogs. And yet here you are, staring at
I shrank a 2.3 GB Docker image without doing anything clever Read More »
No, API gateway is not a “fancy load balancer”, it doesn’t secure your APIs like a API gateway. Think of them as two different tools, not competing ones. ALB – Helps guide web requests to the right service. NLB – Moves network traffic fast and keeps connections steady. API Gateway – Checks requests, applies rules,
When you can deploy with CI/CD pipelines? Most CI/CD pipelines stop once they push an image or run a deploy script. That’s where the difference starts.. GitOps tools like ArgoCD and Flux keep clusters in sync with Git, not with whatever the last pipeline happened to run. They give you versioned config, automatic rollbacks, continuous