The bus itself is extremely lightweight -- it can handle millions of messages per second. The main bottleneck is the cost of marshalling. And we comfortably achieve throughput in the 100s of thousands per second on a modest server.
The bottom line: it's pretty fast.
Thank you, that's very promising.
What about memory and resource usage? How much does it cost to simply have a service available (without any messages being sent)? Is ErraiBus keeping connections open or something like that? (I suppose this really only applies to services with one endpoint on the server and the other on the client.)
1 of 1 people found this helpful
There's only one connection which is kept open to a client, and the connection is essentially multiplexed by service name. Thus, the cost of having a service is only the cost of a string in a Map with an object pointer to the service handling callback code. It doesn't get lighter weight than that. =)
Excellent! Just what I wanted to hear. :-)