<?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>Timeout on Micha Kops&#39; Tech Notes</title>
    <link>https://www.hascode.com/tags/timeout/</link>
    <description>Recent content in Timeout on Micha Kops&#39; Tech Notes</description>
    <generator>Hugo</generator>
    <language>en</language>
    <copyright>Copyright © 2010 - 2025 Micha Kops. #c7fce1a48044fee97f19975844b0983837a8dc96</copyright>
    <lastBuildDate>Tue, 14 Feb 2017 00:00:00 +0100</lastBuildDate>
    <atom:link href="https://www.hascode.com/tags/timeout/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>
    <item>
      <title>Reactive Programming: Handling Service Timeouts and Retries with Retry4j</title>
      <link>https://www.hascode.com/reactive-programming-handling-service-timeouts-and-retries-with-retry4j/</link>
      <pubDate>Wed, 02 Dec 2015 00:00:00 +0100</pubDate>
      <guid>https://www.hascode.com/reactive-programming-handling-service-timeouts-and-retries-with-retry4j/</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;The Reactive Manifesto specifies responsive, resilient, elastic and message-driven as attributes for a reactive application.&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&#34;paragraph&#34;&gt;
&lt;p&gt;When implementing specific mechanisms to achieve this requirements, we often need to deal with timeout and retry-operations in our application and depending on our setup and environment, different tools and libraries exist to help us here.&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&#34;paragraph&#34;&gt;
&lt;p&gt;In the following short tutorial I’d like to demonstrate how to handle exceptions and operation retries on service boundaries with a lesser know, slim library named Retry4j.&lt;/p&gt;
&lt;/div&gt;</description>
    </item>
  </channel>
</rss>
