<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Coupling on JAVAPRO International</title><link>https://javapro-en.svenruppert.com/tags/coupling/</link><description>Recent content in Coupling on JAVAPRO International</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 04 Nov 2025 07:00:01 +0000</lastBuildDate><atom:link href="https://javapro-en.svenruppert.com/tags/coupling/index.xml" rel="self" type="application/rss+xml"/><item><title>How Coupled Are Your Microservices?</title><link>https://javapro-en.svenruppert.com/how-coupled-are-your-microservices/</link><pubDate>Tue, 04 Nov 2025 07:00:01 +0000</pubDate><guid>https://javapro-en.svenruppert.com/how-coupled-are-your-microservices/</guid><description>&lt;p&gt;In this article, we address a crucial topic in software architecture: coupling and its main types in the context of microservices architecture.&lt;/p&gt;
&lt;p&gt;The motivation for this writing comes from direct experience with the negative impact of coupling on system design. In one project, delivered by a software house, we had to fully refactor it before going live due to excessive domain, pass-through, shared data, and content coupling. These interdependencies made the services fragile and undermined their autonomy, scalability, and maintainability.&lt;/p&gt;</description></item></channel></rss>