It's undeniable that among the thousands of innovations that have emerged in the Dev (and Ops more recently) area, one of the most discussed topics is reactive programming. Whether the development of new FWs (Frameworks), such as the implementation for the Java language of ReactiveX (RxJava), the recent launch of Spring 5 with reactive programming, or even the launch of lambdas and streams in Java 8 (since 2014 ), it is clear that more and more reactive thinking is becoming present in the code and FWs that we use.
Since I am a Java Dev, I will try to comment here on what the main options Java developers today count on to create their applications. This can be a great option in various situations of the day-to-day programming, always remembering that it is important to evaluate the real need to use a complex or expensive resource to solve a problem (the famous ant-killing cannon). However, before leaving comments on the tooling that I see as the state of the art for reactive programming, I would like to briefly highlight the famous pillars of this paradigm (according to the Reactive Manifesto):
from DZone.com Feed https://ift.tt/2tGlWG9
No comments:
Post a Comment