Don’t Let Your Microservice Get Put in Timeout

The Problem

java.net.SocketTimeoutException: Read timed out
requests.exceptions.ConnectionError (Caused by <class 'socket.error'>: [Errno 104] Connection reset by peer) 
ERR proxy: error connecting to 10.131.16.144:8081: dial tcp 10.131.16.144:8081: i/o timeout

Background

  • The network is reliable.
  • Latency is zero.
  • Bandwidth is infinite.
  • The network is secure.
  • Topology doesn’t change.
  • There is one administrator.
  • Transport cost is zero.
  • The network is homogeneous.

Solutions

  1. Retry upon failure
  2. Investigate messaging architectures
  3. Check your proxy settings

If at first you don’t succeed

Apache JClouds Example

Take a Number

What To Do About Walls

Conclusion

--

--

--

Manage Developer Relations @Dolby; Maker at Robot Garden; Previously HERE, GE, Rackspace, DreamWorks Animation, MathWorks, Carnegie Mellon

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Your code is disposable, for your own good

Advance Animation in SwiftUI

On the Go!

Deploy a simple flask application in Google Cloud Run

{UPDATE} マスター オブ カオス Hack Free Resources Generator

Navigation System inside Warehouse

An Introduction to Linear Search

What’s Trending in the Dev Community?

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Jayson DeLancey

Jayson DeLancey

Manage Developer Relations @Dolby; Maker at Robot Garden; Previously HERE, GE, Rackspace, DreamWorks Animation, MathWorks, Carnegie Mellon

More from Medium

Microservices Part I

NoSQL and MongoDB

Version Controlling | NoSql

What is NoSQL?