3 ms·
Hi, I'm currently in the researching & prototyping phase of what's the best and will-be-the-most-community supported distributed real time distributed framework
by noname123 13y ago
Hi, I'm currently in the researching & prototyping phase of what's the best and will-be-the-most-community supported distributed real time distributed framework based on the reactor pattern?
So far, I've got:
Queuing Framework (rolling your own streams):
1) ZeroMQ (language agnostic, so have to roll your own serialization and services, seems like Google Protocol Buffer is the best way to go)
2) RabbitMQ (relies on a central message broker, with lots of built-in bindings)
Event-Based Frameworks:
2) Akka (JVM)
3) RxExtensions (.net) but have RxCpp and RxJava ports
4) Reactor (JVM)
Stream-Based Frameworks
4) Twitter Storm (Java-ish, but suppose to be language agnostic?)
5) S4 (Java-ish, but suppose to have bindings?)
Can any peeps help me out on your opinion what is the best or give me a better one? Currently, I'm having fun multiplexing sockets, dereferencing C pointers and seg-faulting, so any suggestion is welcome.
- noelwelsh 13y agoIF you're looking at RabbitMQ you should take a look at Kafka. Overall, I think looking for one framework to-rule-them-all is a mistake. Different components demand different tradeoffs.
- tegeek 13y agoYou would like Storm http://storm.incubator.apache.org/ http://storm.incubator.apache.org/
- eweise 13y agoCheck out Amazon Kinesis for messaging.