To ZMQ or to XS: ArchLinux ARM
See below: I'm less concerned the cross-language support is there, looks like enough work is put into C#
.NET, could be used there as well as C++. Our 64 million dollar question is: has anyone cross compiled into
ArchLinux ARM yet?
I am responsible for designing an embedded device which I believe will have embedded and non-embedded,
intra-process, and inter-process, messages passing between various architectural components, and
several potentially viable technologies have revealed themselves as candidates in this horse race.
While I don't consider myself a betting man, per se, I would like to leverage this technology for
infrastructure so that I can focus on solving present problems instead of bogging down in inter-thread
comm, event brokering, IPC, and a whole host of related issues.
Also, to give you an idea, CORBA and ZeroC Ice have also been considered. CORBA less attractive for bloat,
design-by-committee reasons, and ZeroC Ice has its own set of challenges: technically, is very fast,
extends directly into the object model allowing me to focus on the servant/client relationship, also
instead of infrastructure.
So... What's the story with the ZMQ / XS fork in the road? In either case, more work is involved, adapters are
required around or among the mix of comm "pipes", whether we're talking about a file transfer chunker (per
se), number crunching data factory producer/consumer, event brokering messaging system, what have you.
Serialization issues can be addressed. As can SOLID architectural decisions like extending into a
distributed event model, etc. The right kind of SOLID design can permit an extensible, maintainable
design around either technology. As regards ZMQ or XS, I'm more concerned with the fork and stability of
either or both infrastructures. I believe I've seen a post enumerating the ZMQ roadmap as well as XS. Along
Also, are there any benchmark numbers comparing / contrasting latency and throughput outcomes?