<?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>Microservices on Thomas Cothran</title><link>https://thomascothran.tech/tags/microservices/</link><description>Recent content in Microservices on Thomas Cothran</description><generator>Hugo</generator><language>en</language><copyright>2023, Thomas Cothran</copyright><lastBuildDate>Sun, 23 Jul 2023 00:00:00 +0000</lastBuildDate><atom:link href="https://thomascothran.tech/tags/microservices/index.xml" rel="self" type="application/rss+xml"/><item><title>Brittle Clojure: Creating Legacy Clojure Systems</title><link>https://thomascothran.tech/2023/07/brittle-clojure/</link><pubDate>Sun, 23 Jul 2023 00:00:00 +0000</pubDate><guid>https://thomascothran.tech/2023/07/brittle-clojure/</guid><description>Avoid writing brittle Clojure with tactics for flexibility and robustness.</description></item><item><title>Distributed Merges and Continuous Integration</title><link>https://thomascothran.tech/2023/07/distributed-merges/</link><pubDate>Fri, 14 Jul 2023 00:00:00 +0000</pubDate><guid>https://thomascothran.tech/2023/07/distributed-merges/</guid><description>Feature branching with large monoliths causes merge hell. Microservices promise independent deployability. But sometimes you get distributed merge hell</description></item></channel></rss>