15 ms·
I worked on such a site in the mid-2000s. TIBCO Rendezvous was extremely efficient in the steady state, but boy, it had a catastrophic failure mode: during net
by otterley 10y ago
I worked on such a site in the mid-2000s. TIBCO Rendezvous was extremely efficient in the steady state, but boy, it had a catastrophic failure mode: during network congestion or receiver saturation, it would start repeating messages, causing the network congestion and saturation to worsen. The only way to stop the bleeding was to shut everything down.
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.
- tptacek 10y agoThis 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).
- otterley 10y agoBack 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. :)
- tptacek 10y agoDepends on what you mean by "from a network perspective". Bandwidth? Sure. Network processing? Not so much: multicast is expensive for routers.
- deleted 10y ago[deleted]
- SEJeff 10y agoMost 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.
- polskibus 10y agoWhat did they replace it with?
- SEJeff 10y agoNon-open source proprietary systems, as one does :/
- kasey_junk 10y agohttps://github.com/real-logic/Aeron https://github.com/real-logic/Aeron Is well regarded & open source
- SEJeff 10y agoSeveral 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/specifications/dataproducts/moldudp.pdf https://www.nasdaqtrader.com/content/technicalsupport/specif... It is actually quite good.