<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Devops on Joshua Antony | Tech Blog</title><link>https://blogs.joshuaantony.com/tags/devops/</link><description>Recent content in Devops on Joshua Antony | Tech Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 02 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blogs.joshuaantony.com/tags/devops/index.xml" rel="self" type="application/rss+xml"/><item><title>Overengineering Microservices: When Smart Decisions Compound Into Complexity</title><link>https://blogs.joshuaantony.com/posts/overengineering-microservices/</link><pubDate>Thu, 02 Apr 2026 00:00:00 +0000</pubDate><guid>https://blogs.joshuaantony.com/posts/overengineering-microservices/</guid><description>HAProxy sidecars for mTLS. Hystrix for circuit breaking. Apache Camel between layers within the same service. Six API versions. A mandated common framework. A squash merge ban. Each decision was defensible. Combined, they created a system that took three months to onboard into.</description></item><item><title>Katalon Is Obsolete: Open Source Has Won</title><link>https://blogs.joshuaantony.com/posts/katalon-is-obsolete/</link><pubDate>Wed, 25 Mar 2026 00:00:00 +0000</pubDate><guid>https://blogs.joshuaantony.com/posts/katalon-is-obsolete/</guid><description>Katalon solved a real problem for its era: giving non-coding QA teams a path to automation. That problem has been solved more effectively by open-source frameworks and AI code generation.</description></item></channel></rss>