When starting with Reactive Programming, some operators are easy to grasp and some are rather difficult to understand. Some operators share a common purpose, like map and flatMap that both transform the input type into some potential different output type. …
Today’s blog post stems from a recent discovery in a customer project. We are maintaining a service that was suffering from a performance problem. The service prepares infrastructural data from various sources and offers them to the outside world, nothing extraordinary. …
Today, at peak times customer facing applications often have to cope with tens of thousands or more simultaneous requests. While cloud computing and the accompanying possibilities of dynamic scaling of applications help to overcome this, they also reach their limits at some point. …
At Digital Frontiers we all have our favourite languages. The other day we were arguing about advantages and shortcomings of some specific ones and decided to have a closer look at them, using a Sudoku verifier as common example. …
In my last blog post, I gave you an introduction to reactive programming that was meant to explain when to use and, even more important, when not to use reactive programming. This emerging programming paradigm is initially anything but easy to grasp. …
Reactive Programming has long since begun its journey from pure web applications to Java Enterprise applications. It promises higher performance and lower memory footprints through the use of asynchronous non-blocking calls.
Most likely, you already read some documentation and blog posts about Reactive Programming or one of its implementations in…
Every programmer knows this situation. At some point, you come across a piece of code that is so full of nested if, else and case statements that you sit in front of the screen shaking your head for a while. The reasons for code like this are numerous. The application…
In all of my recent projects as a consultant, a microservice architecture was selected to reduce the interdependency between business functionality by organizing services around business capabilities. In these projects, JSON over HTTP (in a more or less REST-ful way) is usually the first choice for inter-service communication.
Speaking with some developers (mostly having a Java background) you will sooner or later hear a quotation like “Optional is a safe way for handling null”. …
