<?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>Stability-Patterns on Micha Kops&#39; Tech Notes</title>
    <link>https://www.hascode.com/tags/stability-patterns/</link>
    <description>Recent content in Stability-Patterns on Micha Kops&#39; Tech Notes</description>
    <generator>Hugo -- 0.147.8</generator>
    <language>en</language>
    <copyright>Copyright © 2010 - 2025 Micha Kops. #213243b1d6e8932079e09227d3f3ed0c806cd0c9</copyright>
    <lastBuildDate>Tue, 14 Feb 2017 00:00:00 +0100</lastBuildDate>
    <atom:link href="https://www.hascode.com/tags/stability-patterns/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Resilient Architecture in Practice – Circuit Breakers for Java: Failsafe, Javaslang, Hystrix and Vert.x</title>
      <link>https://www.hascode.com/resilient-architecture-in-practice-circuit-breakers-for-java-failsafe-javaslang-hystrix-and-vert.x/</link>
      <pubDate>Tue, 14 Feb 2017 00:00:00 +0100</pubDate>
      <guid>https://www.hascode.com/resilient-architecture-in-practice-circuit-breakers-for-java-failsafe-javaslang-hystrix-and-vert.x/</guid>
      <description>&lt;div id=&#34;preamble&#34;&gt;
&lt;div class=&#34;sectionbody&#34;&gt;
&lt;div class=&#34;paragraph&#34;&gt;
&lt;p&gt;When dealing with remote services or APIs there is always the risk of latency issues, failures or connection losses. The worst thing to happen is when the remote service is down and our application hangs until the underlying protocol’s (e.g. TCP) connection timeout is reached and we’re receiving an exception. Until this moment is reached, our application might hang, memory is allocated for threads or bound objects and at last, our continuous requests might prevent the remote system from recovering.&lt;/p&gt;
&lt;/div&gt;</description>
    </item>
  </channel>
</rss>
