[jboss-dev-forums] [Design of Messaging on JBoss (Messaging/JBoss)] - Re: DB performances for large number of messages

[timfox]

One other thing you should think about is your application design.

In general, high volume data is *not* persistent. E.g. market data feed where messages are shot out very fast with low latency, and the application is designed to cope with loss of messages. If it doesn't get a particular message, that's fine it will get another one shortly whose result (the price) will override the previous one anyway.

Quite often you can "design out" persistence at the application level.

If your data is non persistent then the system will be able to handle much larger volumes and wil scale much better since it doesn't have to persist through the bottleneck - the database.

So I'd ask the question - does the data really need to be persistent? How long do your messages live for?

Perhaps you could explain your use cases in more detail?




View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4054653#4054653

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4054653