by lgsilver on 6/8/15, 4:08 PM with 1 comments
by eip on 6/8/15, 8:07 PM
Storm is ok. It's not very DI friendly and the documentation is not the best. It only supports pull when for our use cases push would always be preferable.
Twitter announced a replacement for Storm called Heron but no word on if/when it will be released. It's supposed to be much faster.
Storm is nice in that it enforces patterns for message passing (spouts/bolts). So the code ends up being pretty clean and easy to understand.
We use a small library on top of Storm to add Spring support.