Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>This isn't an easy question to answer, as there are many parts to latency. If your building a publish-subscribe methodology, you should look at multicast protocols or UDP.</p> <p>What are your requirements? Are these devices on the same flat network, will you be crossing boundaries (firewalls, switches, routers)? All of these little things are part of the bigger picture. </p> <p>Once you get into UDP and Multicast, you going to need to deal with packet loss, packet retransmission, message ordering, message completion and a host of other things to deal with. That's why most buy products like Tibco and some of the other message bus technologies to deal with this. </p> <p>If your looking for Wall St. type latency, you getting into the bounds of dedicated routers / firmware. </p> <p>You also don't really define what you mean by latency. I gather your looking at network latency, which is limited by the speed of light (sorry it's the law!) over distance. </p> <p>Latency can also be the time your code responds to some event as well. </p> <p>Edit 1: </p> <p>IP Multicast is your best bet, as it is reasonably well understood and is routable across lan's assuming you have a decent networking infrastructure. </p> <p>I see an open source project <a href="http://www.jgroups.org/" rel="nofollow">JGroups</a> that looks to have something. You might want to look at Actors <a href="http://doc.akka.io/docs/akka/1.3.1/java/remote-actors.html" rel="nofollow">Remote Actors</a> as well, I don't have any experience with either of these projects, so your mileage may vary. </p> <p>For Commercial software I would look at Tibco. I'm not sure of their product packaging anymore, but they used to have Tib Rendezvous (Tib RV) and an older product (can't remember the name off the top of my head), I've used both to process Market Data. </p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload