Re:Say No to Paxos Overhead: Replacing Consensus with Networ...
by tptacek on Friday December 09, 2016 @12:18PM
(#13140027)
This is my experience with Rendezvous as well. The very largest financial organizations using Tibco tend to have a whole group of engineers whose only job is to keep Rendesvous from throwing a rod. Their networks are also overprovisioned and their traffic rates are pretty straightforward to characterize.
You can, of course, use Rendezvous without multicast.
And: does anyone still use it? The last exchange I worked with that did was migrating from it to JMS (which sort of gives lie to the idea that Rendezvous's multicast performance was that big a deal).
Re:Say No to Paxos Overhead: Replacing Consensus with Networ...
by otterley on Friday December 09, 2016 @01:58PM
(#13140897)
Back in the 1990s and early 2000s, network bandwidth and server capacity was a lot lower, so IP multicast was the most efficient way to distribute data to hundreds or thousands of clients.
Now that 10Gb+ is commonplace and modern servers can service hundreds or thousands of message bus consumers with efficient kernel-managed event loops, yes, it's arguably less needed now. But nobody will claim it's efficient from a network perspective. :)
Re:Say No to Paxos Overhead: Replacing Consensus with Networ...
by tptacek on Friday December 09, 2016 @02:15PM
(#13141016)
Depends on what you mean by "from a network perspective". Bandwidth? Sure. Network processing? Not so much: multicast is expensive for routers.
Re:Say No to Paxos Overhead: Replacing Consensus with Networ...
by SEJeff on Friday December 09, 2016 @03:05PM
(#13141395)
Most financial firms (HFTs like I work for at least) purged Tibco with scorn and hellfire long ago due to reasons like the ones you just mentioned.
Re:Say No to Paxos Overhead: Replacing Consensus with Networ...
by polskibus on Friday December 09, 2016 @03:59PM
(#13141799)
What did they replace it with?
Re:Say No to Paxos Overhead: Replacing Consensus with Networ...
by SEJeff on Friday December 09, 2016 @04:47PM
(#13142134)
Non-open source proprietary systems, as one does :/
Re:Say No to Paxos Overhead: Replacing Consensus with Networ...
by kasey_junk on Friday December 09, 2016 @06:32PM
(#13142829)
https://github.com/real-logic/Aeron
Is well regarded & open source
Re:Say No to Paxos Overhead: Replacing Consensus with Networ...
by SEJeff on Saturday December 10, 2016 @06:50PM
(#13148681)
Several firms (not the one I currently work for) have implemented their own variants of NASDAQ's "MOLD" reliable udp protocol:
https://www.nasdaqtrader.com/content/technicalsupport/specif...
It is actually quite good.
At any rate, most cloud SDNs don't support IP multicast (unless you use an overlay like Weave), so it's sort of a nonstarter for them.
These days I might use Redis pub/sub along with a multi-level cache (e.g. LMDB + local Redis + remote Redis) if I need to distribute data to a large number of clients efficiently.