Patience pays off. How long running services reduce complexity by Bernd Rucker
386 views · Published 27 March 2018 · 53:38 · Indexed 22 October 2026
Channel: Devoxx · 2018 · Science & Technology
“Let’s throw an error” - developers are often quick with this decision as it makes life easier in that moment. But dumping failures to clients noticeable increases the overall system complexity. “Please try again in a few minutes”. Introducing long running behavior can drastically improve this situation. We will look at multiple interesting patterns of long running behavior in this talk. Services could for example react immediately but switch to asynchronous responses with persistent state when leaving the happy case. This allows to take seconds, minutes or even weeks to sort out failures which can involve waiting for services to become available or humans to intervene. Doing so, even if only for the failure case, makes everybody’s life easier. In this talk we want to iterate over various patterns by showing concrete examples. We will also give hints on proper implementations using hands-on source code examples.
More from this channel
-
32:13
Writing Groovy AST Transformations: Getting Practical in an hour! by Baruch Sadogursky
-
25:58
TweetWallFX - Behind the Scenes by Sven Reimers
-
29:44
Second generation "workflow managers" for big data by Alex Van Boxel
-
29:13
Secrets are secrets. Please maintain them as secrets by Alex Soto
-
2:13:40
JavaScript build pipelines with Gulp.js by Stefan Baumgartner
-
2:04:09
Powerful Metaprogramming Techniques With Groovy by Jeff Brown
-
2:38:32
Distributed Machine Learning 101 using Apache Spark from a Browser by Xavier Tordoir/Andy Petrella
-
2:36:21
Caching 101: Caching on the JVM (and beyond) by Alex Snaps/Louis Jacomet