I worked with rxjava and vert.x for one year (before with scala and futures for 2 y.) before not much reactive, and may say: the futures case is middle ground if one wants to find a silver bullet.
So I agree with Jan. We got quite a lot of troubles with RX: learning curve is one thing.
As long as you play with it on workbench all is beautiful and shiny, in reality when whole team working with it, with intensive code reviews one year is not enough, assuming that rx part is one of several parts / microservice (other parts are not rx) - the mental effort to keep all parts by one team on track is not worth it.
I do not talk about vert.x cluster yet and rx part on ui It's different topic.
I belive in 95% cases the rx style is overkill.
Even it one definitely needs one: make sure only one team works on it : they would think only in the nail concepts and be happy with it.
When you’re working with requests and responses, reactive call chains like map eg are just the wrong level of abstraction at that point. It exposes too much technology where you actually need a functional domain abstraction.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I worked with rxjava and vert.x for one year (before with scala and futures for 2 y.) before not much reactive, and may say: the futures case is middle ground if one wants to find a silver bullet.
So I agree with Jan. We got quite a lot of troubles with RX: learning curve is one thing.
As long as you play with it on workbench all is beautiful and shiny, in reality when whole team working with it, with intensive code reviews one year is not enough, assuming that rx part is one of several parts / microservice (other parts are not rx) - the mental effort to keep all parts by one team on track is not worth it.
I do not talk about vert.x cluster yet and rx part on ui It's different topic.
I belive in 95% cases the rx style is overkill.
Even it one definitely needs one: make sure only one team works on it : they would think only in the nail concepts and be happy with it.
When you’re working with requests and responses, reactive call chains like map eg are just the wrong level of abstraction at that point. It exposes too much technology where you actually need a functional domain abstraction.