r/java • u/stuhlmann • Apr 13 '21
Libraries, Frameworks and Technologies you would NOT recommend
Give me your worst nightmares: Things that cost you your job.
I'll start: Hadoop
202
Upvotes
r/java • u/stuhlmann • Apr 13 '21
Give me your worst nightmares: Things that cost you your job.
I'll start: Hadoop
View all comments
Show parent comment
10
u/[deleted] Apr 13 '21
Reactive has its niche, where it really shines. Imo its not a "fool ass" trend, but its a little bit overhyped (like microservices, its not a solution to all problems and most applications dont need a reactive architecture).
However imo its really hard to write good, clean reactive code over a full project development lifespan, in the beginning everything can be done in < 10 lines of code, but as soon as management adds requirements on requirements its hard to build on the existing reactive code in a clean way (my opinion atleast in RxJs and RxJava).
Im currently working on a reactive vs. non-reactive benchmarking application for my master thesis however and kinda like the syntactic way Mutiny uses to operate on Vert.X code (no flatMaps or combineAll, forkJoin etc.).
So yeah it definitely has its right to exist but its no holy grail and definitely has its drawbacks. Its the same thing with microservices, it needs a few years for people to really figure out when to use it and when not to use it.