In our distributed system there are native and .NET components, there is a broker that acts both as a network topology explorer and as a message router. Transport and serialization is provided by in-house developed component - it's ugly and buggy.
I'm looking for solutions that provide RPC or messaging and also serialization. I don't need AMQP broker, because it would require additional administration of exchanges and queues. Also I don't need persistence for messages in the system - every such message has value only in real-time.
I know that Thrift offers RPC and also serialization - it works for me only partially, because some communication in our system is based on the PUB/SUB pattern, and Thift isn't suitable for this.
Which ZMQ messaging pattern is suitable for oneway (async) calls? Some components in our system do oneway requests (this is not data distribution, so ZMQ PUB/SUB sockets are not suitable here, as I think). ZMQ REQ/REP sockets are not the option too. Maybe some other patterns?
via Chebli Mohamed
Aucun commentaire:
Enregistrer un commentaire